Use Sequences for sales rep-driven, 1:1 email cadences sent from the rep's own inbox — Sequences are associated with a specific user and require Sales Hub seats; enroll contacts via the Sequences API or HubSpot UI
Use Workflows for automated, marketing-style 1:many communication and internal process automation — Workflows run independently of a specific user and are appropriate for lifecycle management, nurturing, and internal notifications
Enroll a contact in a Sequence programmatically by POSTing to /crm/v3/objects/contacts/{contactId}/sequences with the sequenceId and userId of the enrolling rep; the rep must have a connected inbox
Create or trigger a Workflow enrollment via POST /automation/v4/flows/{workflowId}/enrollments/contacts with the contact email or ID
Check active sequence enrollments for a contact using GET /crm/v3/objects/contacts/{contactId}/associations/sequences and follow the association to retrieve enrollment details
Unenroll a contact from a Sequence by sending a DELETE to the enrollment resource; Workflow unenrollment is managed through the workflow's unenrollment settings or by archiving the workflow
Known gotchas
Sequences require an email sending limit per user per day; API enrollment does not bypass these sending limits — enrolling more contacts than the user's daily sending limit allows will cause emails to queue or fail silently
Workflows and Sequences both have re-enrollment rules but they operate independently — a contact can be simultaneously active in a Sequence and enrolled in a Workflow covering the same communication theme
The Sequences API has limited programmatic management capabilities compared to Workflows — creating or editing Sequence steps via API is not fully supported; use the HubSpot UI for sequence design
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp