HubSpot Trigger
Starts the workflow when a contact or deal is created or changes in your HubSpot CRM.
The HubSpot Trigger checks your HubSpot CRM on a schedule you set, and starts your workflow once for each contact or deal that was created or changed. It reads HubSpot through your workspace's HubSpot connection.
Where you find it
Drag HubSpot Trigger from the Triggers group of an automation project's node palette. A workflow can have several triggers; each one starts the workflow from its own output.
When to use it
- Send a welcome message when a contact is added.
- Tell a team when a deal moves to a new stage.
- Copy contacts or deals into a data store or another system.
Before you start
Connect HubSpot in the project's Integrations tab: select Connect, sign in to HubSpot and approve access. The trigger's Connection list then offers HubSpot (OAuth).
Settings
The panel header has an Enabled / Paused switch. New triggers start Enabled; a paused trigger shows Paused on its canvas card and starts no runs.
Prop
Type
| Event | Starts a run when |
|---|---|
| Contact created | A contact is added. |
| Contact updated | A contact's properties change. |
| Deal created | A deal is added. |
| Deal updated | A deal's properties change, including its stage and pipeline. |
When the trigger first starts, it records your CRM as it is and does not fire for contacts and deals that are already there.
Send test event takes a Sample payload and shows what the trigger would pass to the workflow, without running the workflow's nodes. Recent deliveries lists the latest runs this trigger started, newest first, with their status and duration.
Outputs
| Field | Contains |
|---|---|
input.payload.objectType | contact or deal. |
input.payload.id | The HubSpot record id. |
input.payload.properties | HubSpot's standard properties for the record, such as email, firstname and lastname for a contact, or dealname, amount, dealstage and pipeline for a deal. |
{{state.trigger.type}} is WEBHOOK.
Tips and limits
- The trigger checks HubSpot every few minutes, not the moment something changes. Several changes to one record between checks start one run, with the latest values.
- To act on one stage only, select Deal updated and add a Router or Filter on
input.payload.properties.dealstage. Stages are HubSpot's internal names, such asclosedwon. - Each check picks up to 100 changed contacts and 100 changed deals. If more change between checks, the rest are picked up on the checks that follow.
- Tickets are not available on this trigger.