HubSpot Trigger
The HubSpot Trigger fires your workflow the moment a CRM event happens in HubSpot — such as a new contact being created, a deal stage changing, or a ticket being updated. It works via HubSpot's native Webhook subscription API.
Setup Guide
Step 1: Add the Trigger to Your Workflow
- Add the HubSpot Trigger block as your workflow's trigger.
- Select or create your HubSpot Credentials (OAuth or Private App token).
- Choose the event types you want to subscribe to (e.g.,
contact.creation,deal.propertyChange). - (Optional) Enter your Client Secret from the HubSpot app for webhook signature verification.
- Note the Webhook URL displayed in the settings panel — you will register this in HubSpot.
Step 2: Register the Webhook in HubSpot
- Go to your HubSpot Developer account (opens in a new tab) and open your app.
- In the left sidebar, navigate to Webhooks.
- Click Add new subscription.
- Paste your Webhook URL from Step 1 as the target URL.
- Select the same event types you chose in the block settings (e.g., contact creation, deal property change).
- Click Create subscription and ensure its status is Active.
Tip: To verify webhook authenticity, copy the Client Secret from your HubSpot app's Auth settings and paste it into the trigger's Client Secret field.
Supported Event Types
Events are grouped by CRM object type:
| Group | Events |
|---|---|
| Contact | contact.creation, contact.deletion, contact.privacyDeletion, contact.propertyChange |
| Company | company.creation, company.deletion, company.propertyChange |
| Deal | deal.creation, deal.deletion, deal.propertyChange |
| Ticket | ticket.creation, ticket.deletion, ticket.propertyChange |
| Product | product.creation, product.deletion, product.propertyChange |
| Line Item | lineItem.creation, lineItem.deletion, lineItem.propertyChange |
| Conversation | conversation.creation, conversation.deletion, conversation.newMessage, conversation.propertyChange |
You can subscribe to multiple event types in a single trigger block.
Response Data
When the trigger fires, the following values are available as workflow variables:
| Variable | Description |
|---|---|
objectId | The HubSpot object ID (contact, deal, etc.) that triggered the event |
subscriptionType | The normalized event type (e.g., contact.creation) |
portalId | Your HubSpot portal (account) ID |
propertyName | For propertyChange events: the property that changed |
propertyValue | For propertyChange events: the new value of the property |
changeSource | What caused the change (e.g., CRM, IMPORT, API) |
eventId | Unique identifier for the webhook event |
occurredAt | Unix timestamp of when the event occurred |
fullPayload | The complete raw JSON payload from HubSpot |
Webhook Signature Verification
HubSpot signs outgoing webhook payloads with your app's Client Secret using a SHA-256 HMAC. When a Client Secret is configured in the trigger settings, InditeAI will validate each incoming request and reject any that fail signature verification — protecting your workflow from unauthorized calls.
To enable this:
- Open your HubSpot app → Auth → copy the Client Secret.
- Paste it into the Client Secret field in the trigger settings panel.
Example Use Cases
- Lead routing: When a new contact is created with a specific lifecycle stage, automatically assign them to a sales rep and send a Slack notification.
- Deal updates: When a deal moves to
Closed Won, trigger a contract generation and send a welcome email to the customer. - Ticket escalation: When a support ticket's priority changes to
High, create a Jira issue and notify the on-call engineer. - Data sync: Mirror HubSpot contact property changes to an external database or Google Sheet in real-time.
- Conversation handoff: When a new conversation message arrives, route it to an AI agent for an automated first response.
Troubleshooting
Workflow not triggering?
- Confirm the webhook subscription in HubSpot is Active.
- Ensure the workflow is Published and Active in InditeAI.
- Verify the Webhook URL in HubSpot exactly matches the URL shown in the trigger settings.
- Check that the subscribed event types in HubSpot match those selected in the block.
Signature verification errors?
- Ensure the Client Secret in the trigger settings matches the one from your HubSpot app's Auth tab.
- HubSpot sends signatures as
X-HubSpot-Signature. Make sure no proxy is stripping this header.
propertyName / propertyValue are empty?
- These fields are only populated for
*.propertyChangeevents. Other event types (e.g.,contact.creation) will not include them.