Runner.Featured workflow
Inbox Follow-Through for Gmail, Calendar, and Drive
Important threads move from inbox clutter to prepared follow-through.
CONNECTOR
Local Files
Local Files connector
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.
Local Files in real workflows
The app page is only useful if it shows how Local Files fits into a real job. This preview is pulled from the live workflow pages that already use the connector.
+New Session
Sessions
Connected apps
GitHub
Google Drive
Local Files
GitHubGoogle Drive+
Connect a new appWhat would you like to do?
Connected apps
Apps used with Local Files
Why it's better
Local Files is more useful inside a workflow
- 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.
Common pairings
Local Files often works with
Related workflows
Public workflow pages where Local Files is part of the connected stack.
Priority founder inbox follow-through
Inbox Follow-Through for Gmail, Calendar, and Drive
Important threads move from inbox clutter to prepared follow-through.
Gmail
Google CalendarGoogle DriveLocal FilesLuminance monthly investor update
Turn Granola Notes Into Investor Updates
Investor reporting becomes a structured workflow instead of a recurring scramble.
GranolaGoogle DriveGmailLocal FilesFounder follow-through before next week's meetings
Gmail + Calendar + Drive Follow-Through
Follow-through stops stalling between inbox, docs, and calendar.
GmailGoogle CalendarGoogle DriveLocal FilesWhat Runner can do with Local Files
These examples are grounded in the real Runner backend connector definitions and connector guidance docs, not generic marketing filler.
Local Files
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.
Local Files
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.
Local Files
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.
How this connector is wired in Runner
Provider
Runner
Category: Desktop context.
Backend
Local file access
Built into Runner's desktop workflow model so local context can be read before cloud actions begin.
What to expect when Runner uses Local Files
Operational note
Local Files
This is what makes Runner materially different from browser-only assistants.
Testimonials
People using Runner to get more done with Local Files
The value is the same across connectors: real context in, real work out, no copy-paste operating model.
“I got hours back every week. Runner handles the follow-through work that used to sit open across tabs and docs.”
Jordan Rogers
@jordanrogers
“It gives me one place to work across email, calendar, and docs. The time savings are real.”
Lynn Marshall
@lynnmarshall
“I stopped losing deals to slow follow-up. Runner drafts the reply and schedules the next step before I forget.”
Danielle Okafor
@danielleokafor
“Runner connects my CRM, email, and meeting notes so I actually prep for calls instead of winging it.”
Aisha Patel
@aishapatel
“What used to take half a day now takes one focused pass in the morning.”
Rajat Singh
@rajatsingh
“Meeting follow-up used to die in my notebook. Now the recap, emails, and calendar items happen before I leave the room.”
Ethan Park
@ethanpark
“I tried every productivity tool on the market. Runner is the first one that actually finishes work instead of just organizing it.”
James Wright
@jameswright
“Board prep went from a full Sunday to a one-hour Monday morning workflow. The context is already assembled.”
Priya Nair
@priyanair
“The morning briefing workflow changed how I start every day. I see blockers, priority threads, and follow-ups before the first meeting.”
Sarah Kim
@sarahkim
“The double opt-in intro workflow is the single most useful thing I have run this quarter. Warm intros used to take 20 minutes each.”
Marcus Chen
@marcuschen
“Investor updates that used to take a full day now come together in 45 minutes from real data.”
Oliver Reeves
@oliverreeves
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.