Skip to main content
Default connects to HubSpot with a single HubSpot sign-in. Once connected, Default workflows start when HubSpot contacts, companies, and deals are created or updated, read and write standard and custom objects, log engagements, and set record owners from Default queues. Default can also import HubSpot records into its own data every hour.
Select Settings in the sidebar, then Connections under Workspace Settings, and open HubSpot. Admin access is required.

​
What Default supports in HubSpot

Data sync and triggers only read from HubSpot. Default changes HubSpot records only when a workflow node writes to them, or when someone confirms a crm_write update through the MCP server (Beta).

​
Connect HubSpot to Default

1

Open HubSpot

Select the HubSpot card on the Connections page.
2

Authorize the connection

Select Connect and approve Default in the HubSpot authorization window. You don’t create a HubSpot app or use a developer account.
3

You're connected

The HubSpot page shows Data sync and Watched fields, and the HubSpot card on the Connections page shows a check mark. Default also starts mapping members to HubSpot owners by email.
If an earlier connection was left half-finished, Connect on the HubSpot page reads Reconnect.

​
What connecting HubSpot needs

Default’s reads and writes go through the connection the approving HubSpot user created. Make sure that user can see and edit every object and property your workflows use.

​
HubSpot objects Default supports

Engagement nodes work with Note, Call, Meeting, Task, Email, and Postal mail. For every node’s fields, see CRM nodes. To act on a HubSpot custom object when something changes, trigger on the related contact, company, or deal, then find the record with Match Record.

​
Workflow triggers from HubSpot

2 triggers start a workflow from a HubSpot record. Both appear once HubSpot is connected and use the same fields:
  • CRM Record Created fires when a new record of that object appears in HubSpot.
  • CRM Record Updated fires when an existing record changes. A Condition that uses Fields Updated limits it to changes in the properties you name.
Deleting a record, or changing an association between records, does not start a workflow.

​
How HubSpot changes reach Default

Default picks up HubSpot changes in 2 ways, and neither needs setup in HubSpot:
  • New records. HubSpot notifies Default through Default’s own HubSpot app when a contact, company, or deal is created.
  • Updated records. Default checks HubSpot for changed records every few minutes and starts the matching workflows.
You don’t create HubSpot workflows, webhooks, or a private app for Default. When you publish a workflow with a HubSpot CRM Record Created trigger, Default sets up new-record delivery for that object before the new version goes live:
  • Publishing can need an admin. If a publish needs Default to change what it subscribes to in HubSpot, the person publishing must be an admin in Default. Otherwise the publish stops with a message asking an admin to publish the workflow once.
  • A failed setup blocks the publish. If Default can’t set up delivery, the workflow is not published and the previously published version keeps running.
A CRM Record Updated trigger needs no setup at publish. Default starts checking that object for changes once the workflow is published.

​
Data sync

Data sync on the HubSpot page imports HubSpot records into Default. It lists Company, Contact, and Deal. How Data sync works:
  • The first sync imports every existing record of the object. For Deal, the first import covers open deals only.
  • After that, Default refreshes the object every hour.
  • Adding properties to an object that is already syncing imports those properties for existing records too.
  • Companies become Company records in Default, contacts become Person records, and deals become Opportunity records. To choose which source fills each Company or Person field, see Objects.
Data sync and workflow triggers are separate. Starting or stopping a sync doesn’t change which workflows run, and triggers work with Data sync off.

​
Watched fields

Watched fields shows what Default monitors in HubSpot for your workflow triggers. It carries a Managed by workflows badge and is read-only: your published workflows with CRM Record Created or CRM Record Updated triggers set it. Select View workflows to open them. Each object, Company, Contact, and Deal, shows its current state:

​
What Default writes to HubSpot

Default writes to HubSpot only from the workflow nodes you add, and from confirmed crm_write calls through the MCP server (Beta): When a node writes the owner property (hubspot_owner_id), Default converts the chosen Default user into their HubSpot owner ID through that user’s mapping. A write for a user without a mapping fails.

​
Map Default users to HubSpot owners

Every Default user who owns HubSpot records needs a HubSpot owner mapping.
  • Automatic mapping. When HubSpot connects, Default matches each member’s email to a HubSpot owner and saves the mapping. It does the same when a new member joins. The HubSpot page shows the result, for example “Auto-mapping complete. Matched 12 out of 14 members by email to HubSpot owners.”
  • Manual mapping. For members whose HubSpot email differs, set their HubSpot Owner ID in Settings → Users: the Owner ID field on the HubSpot card of the member’s Connections page, or the Mappings tab.
  • Invite from HubSpot. When inviting teammates in Settings → Users, Add from HubSpot adds people from your HubSpot account.

​
Limits and behavior to know

​
Disconnect HubSpot

Select Disconnect on the HubSpot page.
Disconnecting takes effect right away:
  • HubSpot triggers stop, and workflow nodes can’t read or write HubSpot.
  • Publishing a workflow with a HubSpot CRM Record Created trigger fails until HubSpot is connected again.
  • Your Data sync settings are removed with the connection.
If you connect HubSpot again, turn Data sync back on for each object, and republish every workflow that uses a HubSpot trigger so Default sets up change delivery again.
Related: Default integrations
Last modified on October 21, 2026