HubSpot Trigger

Overview

Start a workflow when a HubSpot record is created or updated. Choose an object — Contact, Company, Deal, or Ticket — and a delivery mode:

• Real-time webhooks (recommended) — HubSpot pushes events to Falcon Builder the moment they happen. Requires the app's Client Secret on the credential and a webhook target URL configured in your HubSpot app.
• Polling — Falcon Builder checks HubSpot every few minutes via the CRM Search API. No app webhook setup, but slightly delayed.

Real-time setup

• Step 1: Add the app's Client Secret (Auth tab) to your HubSpot credential so we can verify inbound events.
• Step 2: In your HubSpot app under Webhooks, set the target URL to https://www.falconbuilder.dev/api/webhooks/hubspot.
• Step 3: Subscribe to the events you need (e.g. contact.creation, contact.propertyChange) and select the matching events in the trigger node.

We verify HubSpot's v1 request signature (SHA256(clientSecret + body)) on every event and reject anything that doesn't match.

How polling works

• Record created watches createdate; Record created or updated watches lastmodifieddate.
• Each poll returns records changed since the last check, oldest first, so nothing is missed between runs.
• Use Properties to Return to control which fields come back on each record.

Trigger output ($json)

• {{$json.id}} — the record ID
• {{$json.resource}} — the object type (contact, company, …)
• {{$json.event}} — record_created or record_updated
• {{$json.properties.email}} — a returned property
• {{$json.createdAt}} / {{$json.updatedAt}} — timestamps (polling mode)
• {{$json.propertyName}} / {{$json.propertyValue}} — the changed property and its new value (real-time propertyChange events)

Notes

• In created or updated mode, editing a record re-fires the trigger. Branch on a property if you only want to act on certain changes.
• The token needs read scope on the chosen object (e.g. crm.objects.contacts.read).

Required Credentials