Runner.Search contacts, companies, deals, and tickets before creating anything new.
HubSpot Runner Workflows
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.
HubSpotCRM
+New Session
Sessions
Connected appsHubSpot
Gmail
Google Calendar
Attio
HubSpotGmailGoogle CalendarAttio+
Connect a new appWhat would you like to do?
What Runner actually does with HubSpot
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.
Traverse associations so contact, company, and deal context stay connected.
Write updates with the internal property names and data formats HubSpot expects.
Backend surface
Composio toolkit powers this connector inside Runner. Backed by the `hubspot` toolkit in Runner's backend catalog, with connector guidance covering duplicate avoidance, property formats, pagination, and associations.
Operational notes
- The guidance is strict about search-first behavior because duplicate records are easy to create and hard to clean up.
- Dates must be Unix milliseconds, currency fields are string decimals, and enums require internal values, not display labels.
Popular workflows with HubSpot
Real workflow pages where HubSpot is part of the connected stack. Each workflow shows the trigger, connectors, and outcome.
Relationship workflow
Qualify Inbound Leads from Gmail and HubSpot
The inbound lead gets qualified and set up before the opportunity cools.
GmailHubSpotWEWeb SearchRelationship workflow
Stakeholder Research After the First Call
The second meeting is sharper because the account map is already clearer.
WEWeb SearchHubSpotLILinkedIn-style Research
HubSpotLILinkedIn-style ResearchRelationship workflow
Customize the Demo Deck for Prospect Meetings
The deck matches the prospect instead of forcing a generic story.
Granola
Google SlidesHubSpotFounder workflow
Customer Escalation Response Across Support and Sales
Escalations get a thoughtful, context-rich response instead of a rushed reply.
Intercom
Zendesk
SlackHubSpotConnect HubSpot to your favorite apps
Apps that show up alongside HubSpot in real Runner workflows. Each badge links to its own integration page.
Triggers and actions
What Runner can do with HubSpot. These are grounded in the real backend connector definitions, not generic marketing filler.
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.
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.
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.
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.
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.