Runner.Featured workflow
Personal Follow-Through for Family and Life
Personal commitments stop slipping through the cracks between work calendar and message threads.
CONNECTOR
iMessageiMessage connector
Read message history, search conversations, and send texts from the workflow.
Runner accesses iMessage through local macOS APIs for conversation search, message history, and text sending without leaving the workflow.
iMessage in real workflows
The app page is only useful if it shows how iMessage fits into a real job. This preview is pulled from the live workflow pages that already use the connector.
+New Session
Sessions
Connected appsiMessage
Google Calendar
Slack
iMessageGoogle CalendarSlack+
Connect a new appWhat would you like to do?
Connected apps
Apps used with iMessage
Why it's better
iMessage is more useful inside a workflow
- Search message history across individual and group chats.
- Send texts and iMessages without switching to Messages.app.
- Pull conversation context into meeting prep and follow-up workflows.
Common pairings
iMessage often works with
Related workflows
Public workflow pages where iMessage is part of the connected stack.
What Runner can do with iMessage
These examples are grounded in the real Runner backend connector definitions and connector guidance docs, not generic marketing filler.
iMessage
Search message history
"Find my recent messages with Sarah about the dinner plans."
Text message context becomes part of the workflow without opening Messages.
iMessage
Send a text from the workflow
"Send a quick text to the team group chat confirming the meeting time."
Runner sends the message from the workflow instead of requiring a context switch.
iMessage
Search group chats
"Find the group chat with the founding team and show me the last 20 messages."
Group conversation context becomes part of the workflow without opening Messages.
How this connector is wired in Runner
Provider
Apple
Category: Messaging.
Backend
Local macOS access
Uses AppleScript for sending messages and SQLite for reading message history from the local Messages database.
What to expect when Runner uses iMessage
Operational note
iMessage
Requires Full Disk Access for reading message history from the Messages database.
Operational note
iMessage
Only available on macOS — this connector does not work on other platforms.
Testimonials
People using Runner to get more done with iMessage
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 iMessage inside a real workflow
Download Runner to connect iMessage to the rest of your workflow instead of treating it like another isolated tab.