August’s developer updates expand how teams bring data into HubSpot and automate CRM operations. This month introduces webhook data sources for Data Studio, preserves active workflow enrollments when records are merged, and adds app object support to association workflow actions. Together, these changes reduce custom integration work and help automations continue with less manual intervention.
Join the discussion in the Developer Community.
- Stream JSON data into Data Studio with webhook data sources
- Primary records remain enrolled in workflows after merges
- Manage app object associations with workflows
Stream JSON data into Data Studio with webhook data sources
Developers and app partners can now send real-time JSON data from any HTTP-capable system directly into HubSpot Data Studio, without file uploads or a custom connector. Each source provides a unique inbound URL and supports GET, POST, and PUT requests, with options to create records or update existing records using a match key. Requests are currently limited to one record each, and the inbound URL should be treated as a secret because it is the source’s only authentication mechanism. Once ingested, the data can be used in datasets, segments, workflows, and reports; learn more about building and activating datasets in Data Studio.
Primary records remain enrolled in workflows after merges
When two CRM records are merged, the primary record will remain enrolled in its active workflows, preserving its current position, delays, branches, and pending actions. Only the duplicate record being merged away will be unenrolled, allowing data cleanup without interrupting in-flight automation. This change applies automatically to all CRM object types that support merging, and no action is required. Learn more about merging records in HubSpot.
Manage app object associations with workflows
The Manage CRM record associations workflow action now supports app objects from connected apps, allowing workflows to create, update, or remove associations between app object records and other CRM records. This eliminates manual linking and custom automation while making it easier to incorporate app data into existing pipeline, attribution, segmentation, and reporting processes.