Runner.

Local Files Runner Workflows

Pull desktop context into the same workflow as cloud actions.

RunnerDesktop context
What would you like to do?

Popular workflows with Local Files

Real workflow pages where Local Files is part of the connected stack. Each workflow shows the trigger, connectors, and outcome.

Inbox Follow-Through for Gmail, Calendar, and Drive

Priority founder inbox follow-through

Inbox Follow-Through for Gmail, Calendar, and Drive

Important threads move from inbox clutter to prepared follow-through.

Gmail logoGmailGoogle Calendar logoGoogle CalendarGoogle Drive logoGoogle DriveLocal Files
Turn Granola Notes Into Investor Updates

Luminance monthly investor update

Turn Granola Notes Into Investor Updates

Investor reporting becomes a structured workflow instead of a recurring scramble.

Granola logoGranolaGoogle Drive logoGoogle DriveGmail logoGmailLocal Files
Gmail + Calendar + Drive Follow-Through

Founder follow-through before next week's meetings

Gmail + Calendar + Drive Follow-Through

Follow-through stops stalling between inbox, docs, and calendar.

Gmail logoGmailGoogle Calendar logoGoogle CalendarGoogle Drive logoGoogle DriveLocal Files

Connect Local Files to your favorite apps

Apps that show up alongside Local Files in real Runner workflows. Each badge links to its own integration page.

Gmail logoGmail
Google Drive logoGoogle Drive
Google Calendar logoGoogle Calendar
Granola logoGranola

Triggers and actions

What Runner can do with Local Files. These are grounded in the real backend connector definitions, not generic marketing filler.

Read the working folder before drafting

“Use the notes in my local founder folder before you write the weekly update.”

Runner brings private desktop context into the workflow before anything gets written or sent.

Bridge local and cloud source material

“Draft the investor reply from my local diligence notes plus the shared Drive memo.”

The workflow spans your machine and your connected apps without copy-paste handoff.

Use the real file, not memory

“Open the desktop brief for Acme and ground the recap in that file before updating the CRM.”

Outputs stay tied to the actual working document instead of whatever was last pasted into chat.

Use Local Files inside a real workflow

Download Runner to connect Local Files to the rest of your workflow instead of treating it like another isolated tab.

More apps