Add HubSpot Contact Segment Memberships
Add safe contact refs to a verified MANUAL or SNAPSHOT segment.
HubSpot sales and marketing customer-lifecycle provider with capability-scoped OAuth or private-app token readiness.
Connection facts
These details come from the current StackOS provider manifest and action catalog. They describe the available connection—not a promise that every workflow will use every action.
Action catalog
Actions listed for this integration. Individual descriptions note availability limits. A workflow still decides which actions belong in the job and where approval is required.
79 matching actions
Add safe contact refs to a verified MANUAL or SNAPSHOT segment.
Add one verified company-to-deal association label using typed safe refs.
Add one verified contact-to-company association label using typed safe refs.
Add one verified contact-to-deal association label using typed safe refs.
Attach one existing line item to one deal using typed account-bound refs.
Batch upsert companies using a verified unique-property ref and explicit safe property values.
Batch upsert HubSpot contacts using email or an approved unique property.
Deferred until an operator-approved custom-object schema contract exists.
Batch upsert deals using a verified unique-property ref and explicit safe property values.
Batch upsert leads using a verified unique-property ref when Sales write scope is granted.
Batch upsert standalone or existing line items using a provider-verified unique property ref.
Batch upsert products using a provider-verified unique property ref.
App-level webhook Target URL and subscription administration contract; operator-owned because HubSpot requires developer-app authority rather than an installed portal OAuth token.
Log an inbound or outbound call with safe owner and CRM associations.
Create a campaign from the bounded public campaign fields.
Create a timeline note with explicit content, owner, and safe CRM associations.
Create a draft marketing-email asset from a safe template ref or validated stable template path; no recipients or publish state are accepted.
Log a meeting with explicit timing, owner, and safe CRM associations.
Create an assigned sales task with safe CRM associations.
Remove the deal relationship for one existing line item using typed refs.
Deferred until seat, conflict, and enrollment lifecycle behavior has live proof.
Read one campaign and optional bounded asset metrics using a safe campaign ref.
Resolve a safe contact ref internally and read its email subscription states without returning the subscriber email.
Read the current provider state, record count, and selected safe refs for one HubSpot export job.
Read one marketing-email asset and its available post-send statistics through a safe ref.
List custom event definitions and optional property metadata with opaque definition and property refs.
List bounded Marketing Hub campaigns with approved fields and safe campaign, owner, and brand refs.
List portal-aware company fields and custom fields as safe metadata refs.
List the fixed company-to-deal association labels as typed safe refs.
List portal-aware contact fields, custom fields, lifecycle stages, and safe metadata refs.
List bounded membership rows for a safe contact segment ref.
List the fixed contact-to-company association labels as typed safe refs.
List the fixed contact-to-deal association labels as typed safe refs.
List deal pipelines and stages using portal-aware safe refs.
List portal-aware deal fields and custom fields as safe metadata refs.
Deferred until Sales Enterprise entitlement and live contract behavior are proven.
Direct answer
People continue using HubSpot as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.
Common questions
The current catalog includes 79 HubSpot actions across CRM Operations, Lead Management, Outbound Operations, Pipeline Management, Revenue Automation. The exact actions used depend on the workflow and approval rules.
No. HubSpot remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.