Automation Sequences

Name: Automation Sequences API
Brand: Automation Sequences
Availability: InStock

✓ Official Vendor SpecMarketingMarketing Automationoauth2, apiKey4 EndpointsREST

For Agents

Read HubSpot sales sequences and enroll contacts so AI agents can drive one-to-one outreach without leaving an external workflow.

Quickstart

Get started with Automation Sequences in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"enroll a contact in a hubspot sales sequence"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Automation Sequences API.

List the sales sequences configured on a HubSpot portal

Retrieve a single sequence by id with its name and step count

Read the active sequence enrollment for a specific contact

Enroll a contact in a sequence with a chosen sender and start date

GET STARTED

Start building with Automation Sequences API

Explore with Jentic

View OpenAPI Document

The HubSpot Sequences API exposes the sales sequences feature for salespeople doing one-to-one outreach. GET /automation/v4/sequences/ lists the sequences available on the portal, GET /automation/v4/sequences/{sequenceId} returns a single sequence's metadata, GET /automation/v4/sequences/enrollments/contact/{contactId} returns the active enrollment for a specific contact, and POST /automation/v4/sequences/enrollments enrolls a contact in a sequence. Authentication uses OAuth 2.0 access tokens or a private app token sent in the private-app header.

Use Cases

Patterns agents use Automation Sequences API for, with concrete tasks.

★ Auto-enroll inbound leads in the right sequence

When a new lead is created from an inbound form, an integration can immediately enroll them in the sequence that matches their persona. POST /automation/v4/sequences/enrollments accepts a contactId, a sequenceId, and a senderEmail so the right salesperson owns the outreach. The response returns the enrollment id which the integration logs against the lead record.

Call POST /automation/v4/sequences/enrollments with contactId, sequenceId, and senderEmail derived from the lead's territory

Avoid double-enrolment on returning leads

Before enrolling a contact, an integration checks GET /automation/v4/sequences/enrollments/contact/{contactId} to see if there is already an active enrollment. If the response shows an active sequence, the integration skips enrollment and logs the existing one. This prevents salespeople from sending duplicate outreach to the same contact.

Call GET /automation/v4/sequences/enrollments/contact/{contactId} and skip enrollment if the response contains an active sequence id

Pick the right sequence from a list

An ops console renders a dropdown of sequences for a sales rep to choose from. GET /automation/v4/sequences/ lists the sequences on the portal with id and name, so the dropdown stays in sync with what salespeople have built without hand-coding sequence ids in the integration.

Call GET /automation/v4/sequences/ and render the id and name of each result as options in the rep's enrollment dropdown

Agent integration via Jentic

A sales agent watching for new MQLs can enroll them in the matching sequence in real time. Through Jentic the agent searches for the enrollment operation, loads the schema, and executes the call with the lead's contact id, the chosen sequence id, and the assigned rep's email. The HubSpot credential never leaves the Jentic vault.

Search Jentic for 'enroll a contact in a hubspot sales sequence', load POST /automation/v4/sequences/enrollments, and execute with contactId, sequenceId, and senderEmail

Key Endpoints

4 endpoints — the hubspot sequences api exposes the sales sequences feature for salespeople doing one-to-one outreach.

METHOD

PATH

DESCRIPTION

GET

/automation/v4/sequences/

List sales sequences on the portal

GET

/automation/v4/sequences/{sequenceId}

Retrieve a sequence by id

GET

/automation/v4/sequences/enrollments/contact/{contactId}

Retrieve the active sequence enrollment for a contact

POST

/automation/v4/sequences/enrollments

Enroll a contact in a sequence

GET

/automation/v4/sequences/

List sales sequences on the portal

GET

/automation/v4/sequences/{sequenceId}

Retrieve a sequence by id

GET

/automation/v4/sequences/enrollments/contact/{contactId}

Retrieve the active sequence enrollment for a contact

POST

/automation/v4/sequences/enrollments

Enroll a contact in a sequence

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

OAuth access tokens and private app tokens are stored encrypted in the Jentic vault. Sequence calls run through scoped session tokens so the raw HubSpot credential never enters the agent's context.

Intent-based discovery

Agents search Jentic with intents like 'enroll a contact in a hubspot sales sequence' and Jentic returns the matching POST /automation/v4/sequences/enrollments operation with its input schema.

Time to first call

Direct integration: half a day to wire OAuth, lookup logic, and enrollment guards. Through Jentic: under an hour — search, load, execute against the four endpoints.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

HubSpot Automation V4

Workflows handle one-to-many marketing automation while Sequences handle one-to-one sales touches

Use Workflows for nurture campaigns and Sequences for direct sales outreach

Complementary

HubSpot CRM Contacts

Resolve a contact id before enrolling them in a sequence

Use Contacts to look up the contactId required by the enrollment endpoint

Alternative

Salesforce API

Salesforce Cadences are the equivalent of HubSpot Sequences for Salesforce-first organisations

Choose Salesforce when the CRM source of truth and the salesperson workflow live in Salesforce

Alternative

Pipedrive API

Pipedrive offers automated outreach steps for sales reps in its own CRM

Choose Pipedrive when sales runs on Pipedrive rather than HubSpot

FAQs

Specific to using Automation Sequences API through Jentic.

What authentication does the HubSpot Sequences API use?

The spec defines two security schemes: OAuth 2.0 access tokens and private app tokens sent in the private-app header. Both can call all four endpoints. Through Jentic the credential is stored encrypted in the vault.

Can I enroll a contact in a sequence with the Sequences API?

Yes. POST /automation/v4/sequences/enrollments accepts a contactId, a sequenceId, and a senderEmail. The senderEmail must belong to a HubSpot user on the portal because sequence steps send from that user's connected mailbox.

What are the rate limits for the HubSpot Sequences API?

The spec does not declare per-endpoint limits. Sequence calls share the standard HubSpot per-account limit of around 100 requests per 10 seconds for OAuth and private apps. Enrollment-heavy jobs should batch their work to avoid bursts.

How do I check whether a contact is already enrolled?

Call GET /automation/v4/sequences/enrollments/contact/{contactId}. The response returns the active enrollment, including the sequence id and step, or an empty response if the contact is not currently in any sequence.

How do I enroll a contact through Jentic?

Search Jentic for 'enroll a contact in a hubspot sales sequence', load the schema for POST /automation/v4/sequences/enrollments, and execute with contactId, sequenceId, and senderEmail. Jentic returns the new enrollment id.

Can I unenroll a contact through this API?

Not directly. The four exposed endpoints cover listing sequences, reading a sequence, reading a contact's enrollment, and creating an enrollment. To unenroll, the salesperson must end the sequence from the HubSpot UI on the contact record.