Skip to content

HubSpot: Enroll Service Account

HubSpot sequences.enrollmentEnrollServiceAccount: arguments, response, policy and SDK examples.

← Sequences operations · Get started

Operation hubspot.sequences_enrollment_enroll_service_account

Provider route: POST /automation/sequences/2026-09/serviceaccounts/enrollments. Alter supplies the connection’s credentials and routing.

Install @alter-ai/sdk @alter-ai/hubspot with npm, or alter-sdk-hubspot with pip. Supply your connected customer’s grant ID and the arguments described below.

import { App } from "@alter-ai/sdk";
import { HubSpotIntegration } from "@alter-ai/hubspot";
async function execute(input: Parameters<HubSpotIntegration["sequences"]["enrollmentEnrollServiceAccount"]>[0]) {
const app = new App({ apiKey: process.env.ALTER_API_KEY! });
try {
const provider = new HubSpotIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! });
const call = await provider.sequences.enrollmentEnrollServiceAccount(input);
const result = await call.wait();
return result.bodyJson();
} finally {
await app.close();
}
}
import os
from alter_sdk import App
from alter_sdk_hubspot import HubSpotIntegration
async def execute(arguments):
async with App(api_key=os.environ["ALTER_API_KEY"]) as app:
provider = HubSpotIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]})
call = await provider.sequences.enrollment_enroll_service_account(arguments)
result = await call.wait()
return result.body_json()
FieldTypePresenceDescription and constraints
$objectRootAdditional keys: not allowed
bodyModelRequired within parentExpand Enroll a contact — request body — body

Referenced models: Enroll a contact — request body — body

Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.

FieldTypePresenceDescription and constraints
$ModelRootExpand Enroll a contact — response body

Referenced models: Enroll a contact — response body

Enroll a contact — response body
FieldTypePresenceDescription and constraints
$objectRoot
enrolledAtstringRequired within parentThe date and time when the contact was enrolled in the sequence, in ISO 8601 format.
Format: date-time
idstringRequired within parentThe unique identifier for the sequence enrollment.
toEmailstringRequired within parentThe email address of the contact who is enrolled in the sequence.
updatedAtstringRequired within parentThe date and time when the sequence enrollment was last updated, in ISO 8601 format.
Format: date-time
Enroll a contact — request body — body
FieldTypePresenceDescription and constraints
$objectRoot
contactIdstringRequired within parentThe unique identifier of the contact to be enrolled in the sequence. It is a string.
senderAliasAddressstringOptionalAn optional alias email address that can be used as the sender's address. It is a string.
senderEmailstringRequired within parentThe email address of the sender responsible for the sequence enrollment. It is a string.
sequenceIdstringRequired within parentThe unique identifier of the sequence in which the contact is to be enrolled. It is a string.

SDK function policy ID: hubspot.sequences_enrollment_enroll_service_account. Catalog operation: sequences_enrollment_enroll_service_account. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.

Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.

Required provider scopes: ["automation.sequences.enrollments.write"]

Official provider source

Report an issue with this page

Necessary

Required for sign-in, security, authorization, and remembering your choices.

Always active

Analytics

Helps us understand which product and documentation features are useful.

Performance diagnostics

Uses performance tracing and privacy-masked session replay to diagnose problems.

You can change these choices at any time from Cookie settings.