Runner.Featured workflow
Qualify Inbound Leads from Gmail and HubSpot
The inbound lead gets qualified and set up before the opportunity cools.
CONNECTOR
HubSpotHubSpot connector
Search before create, follow associations, and keep CRM state synced to the workflow.
Runner exposes HubSpot through the backend `hubspot` toolkit and the Electron app's CRM guidance, which is built around search-first record handling, association traversal, and correct property formats.
HubSpot in real workflows
The app page is only useful if it shows how HubSpot fits into a real job. This preview is pulled from the live workflow pages that already use the connector.
+New Session
Sessions
Connected appsHubSpot
Gmail
Google Calendar
Attio
HubSpotGmailGoogle CalendarAttio+
Connect a new appWhat would you like to do?
Connected apps
Apps used with HubSpot
Why it's better
HubSpot is more useful inside a workflow
- Search contacts, companies, deals, and tickets before creating anything new.
- Traverse associations so contact, company, and deal context stay connected.
- Write updates with the internal property names and data formats HubSpot expects.
Common pairings
HubSpot often works with
Related workflows
Public workflow pages where HubSpot is part of the connected stack.
Acme corp customer qualification
Qualify Inbound Leads from Gmail and HubSpot
The inbound lead gets qualified and set up before the opportunity cools.
GmailHubSpotWEWeb SearchAcme stakeholder research
Stakeholder Research After the First Call
The second meeting is sharper because the account map is already clearer.
WEWeb SearchHubSpotLILinkedIn-style Research
HubSpotLILinkedIn-style ResearchDemo deck customization for Acme
Customize the Demo Deck for Prospect Meetings
The deck matches the prospect instead of forcing a generic story.
Granola
Google SlidesHubSpotVIP account escalation triage
Customer Escalation Response Across Support and Sales
Escalations get a thoughtful, context-rich response instead of a rushed reply.
Intercom
Zendesk
SlackHubSpotWhat Runner can do with HubSpot
These examples are grounded in the real Runner backend connector definitions and connector guidance docs, not generic marketing filler.
HubSpot
Search before creating or updating
HubSpot workflows should search by email, domain, or other identifiers first to avoid duplicates.
"Look up this lead by email and company domain before creating a new CRM record."
Runner starts from the existing CRM state instead of forking duplicate contacts or companies.
HubSpot
Follow associations across the account
Traverse contact, company, deal, and ticket associations to understand the account graph.
"Show me the deals and linked contacts for this company before I draft the follow-up."
Relationship context stays attached to the account rather than spread across isolated objects.
HubSpot
Write the record with correct internal properties
HubSpot updates must use internal property names and the right field formats.
"Update the contact with `hs_lead_status`, add the next step, and set the follow-up date correctly."
Runner produces CRM updates HubSpot will actually accept instead of silently ignoring bad fields.
HubSpot
Paginate and batch large CRM jobs
Large searches should follow the `after` cursor and bulk operations should stay inside HubSpot limits.
"Scan the first 300 inbound leads from the last month and return the ones missing qualification notes."
Runner can do real CRM maintenance work without falling over on paging limits.
How this connector is wired in Runner
Provider
HubSpot
Category: CRM.
Backend
Composio toolkit
Backed by the `hubspot` toolkit in Runner's backend catalog, with connector guidance covering duplicate avoidance, property formats, pagination, and associations.
What to expect when Runner uses HubSpot
Operational note
HubSpot
The guidance is strict about search-first behavior because duplicate records are easy to create and hard to clean up.
Operational note
HubSpot
Dates must be Unix milliseconds, currency fields are string decimals, and enums require internal values, not display labels.
Testimonials
People using Runner to get more done with HubSpot
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 HubSpot inside a real workflow
Download Runner to connect HubSpot to the rest of your workflow instead of treating it like another isolated tab.