HubSpot logo

HubSpot Runner Workflows

Search before create, follow associations, and keep CRM state synced to the workflow.

HubSpotCRM
What would you like to do?

Connect 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.

More apps