Runner.

Local Files Runner Workflows

Pull desktop context into the same workflow as cloud actions.

Runner's local file connector is the bridge between the notes, folders, exports, and working documents on your machine and the cloud tools that need to act on them.

RunnerDesktop context
What would you like to do?

What Runner actually does with Local Files

This page is tied to the real connector definition inside Runner. The highlights below describe the kinds of actions, safeguards, and workflow patterns the app page represents, not a generic integration directory blurb.

Read personal notes and project folders that never made it into a SaaS tool.

Combine desktop files with Gmail, Drive, Calendar, and CRM actions in one pass.

Ground outputs in the working material already on your machine.

Backend surface

Local file access powers this connector inside Runner. Built into Runner's desktop workflow model so local context can be read before cloud actions begin.

Operational notes

  • This is what makes Runner materially different from browser-only assistants.

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.

Relationship workflow

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

Founder workflow

Turn Granola Notes Into Investor Updates

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

Granola logoGranolaGoogle Drive logoGoogle DriveGmail logoGmailLocal Files

Founder workflow

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