Skip to content

HubSpot: Retrieve sequence — sequences get By Sequence Id

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

← Sequences operations · Get started

Operation hubspot.sequences_get_by_sequence_id

Provider route: GET /automation/sequences/2026-09/{sequenceId}. 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"]["getBySequenceId"]>[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.getBySequenceId(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.get_by_sequence_id(arguments)
result = await call.wait()
return result.body_json()
FieldTypePresenceDescription and constraints
$objectRootAdditional keys: not allowed
pathobjectRequired within parentAdditional keys: not allowed
path.sequenceIdstringRequired within parent
queryobjectRequired within parentAdditional keys: not allowed
query.userIdstringRequired within parent

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

FieldTypePresenceDescription and constraints
$ModelRootExpand Retrieve sequence — sequences get By Sequence Id — response body

Referenced models: Retrieve sequence — sequences get By Sequence Id — response body

1 more schema is linked from the tables above, on the schema pages.

Retrieve sequence — sequences get By Sequence Id — response body
FieldTypePresenceDescription and constraints
$objectRoot
createdAtstringRequired within parentThe date and time when the sequence was created, in ISO 8601 format.
Format: date-time
dependenciesarrayRequired within parentAn array of dependencies between sequence steps, each represented by a PublicSequenceStepDependencyResponse object.
dependencies[]ModelEach itemExpand Update sequence — response body — dependencies item
folderIdstringOptionalThe unique identifier for the folder containing the sequence.
idstringRequired within parentThe unique identifier for the sequence.
namestringRequired within parentThe name of the sequence.
settingsModelOptionalExpand Update sequence — response body — settings
stepsarrayRequired within parentAn array of steps included in the sequence, each represented by a PublicSequenceStepResponse object.
steps[]ModelEach itemExpand Retrieve sequence — sequences get By Sequence Id — response body — steps item
updatedAtstringRequired within parentThe date and time when the sequence was last updated, in ISO 8601 format.
Format: date-time
userIdstringRequired within parentThe unique identifier of the user who owns the sequence.

Referenced models: Update sequence — response body — settings, Update sequence — response body — dependencies item, Retrieve sequence — sequences get By Sequence Id — response body — steps item

Update sequence — response body — settings
FieldTypePresenceDescription and constraints
$objectRoot
createdAtstringRequired within parentThe date and time when the sequence settings were created, in ISO 8601 format.
Format: date-time
eligibleFollowUpDaysstringRequired within parentSpecifies the days eligible for follow-ups. Valid values include 'EVERYDAY', 'BUSINESS_DAYS', and 'WEEKDAYS_ONLY'.
Known values: BUSINESS_DAYS, EVERYDAY, WEEKDAYS_ONLY
idstringRequired within parentThe unique identifier for the sequence settings.
individualTaskRemindersEnabledbooleanRequired within parentA boolean indicating whether individual task reminders are enabled.
sellingStrategystringRequired within parentThe strategy used for selling, which can be either 'LEAD_BASED' or 'ACCOUNT_BASED'.
Known values: ACCOUNT_BASED, LEAD_BASED
sendWindowEndMinuteJSONRequired within parent
sendWindowEndMinute (anyOf 1)integerAlternativeThe ending minute of the window during which emails can be sent, represented as an integer.
Format: int32
sendWindowEndMinute (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
sendWindowStartMinuteJSONRequired within parent
sendWindowStartMinute (anyOf 1)integerAlternativeThe starting minute of the window during which emails can be sent, represented as an integer.
Format: int32
sendWindowStartMinute (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
taskReminderMinuteJSONRequired within parent
taskReminderMinute (anyOf 1)integerAlternativeThe minute at which task reminders are sent, represented as an integer.
Format: int32
taskReminderMinute (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
updatedAtstringRequired within parentThe date and time when the sequence settings were last updated, in ISO 8601 format.
Format: date-time
Update sequence — response body — dependencies item
FieldTypePresenceDescription and constraints
$objectRoot
createdAtstringRequired within parentThe date and time when this dependency was created, in ISO 8601 format.
Format: date-time
dependencyTypestringRequired within parentThe type of dependency, which can be either 'TASK_COMPLETION' or 'MANUAL_PAUSE'.
Known values: ADAPTIVE_COMPLETION, MANUAL_PAUSE, TASK_COMPLETION
idstringRequired within parentThe unique identifier for this dependency.
reliesOnSequenceStepIdstringRequired within parentThe unique identifier of the sequence step that this dependency relies on.
reliesOnStepOrderJSONRequired within parent
reliesOnStepOrder (anyOf 1)integerAlternativeThe order number of the step that this dependency relies on.
Format: int32
reliesOnStepOrder (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
requiredBySequenceStepIdstringRequired within parentThe unique identifier of the sequence step that requires this dependency.
requiredByStepOrderJSONRequired within parent
requiredByStepOrder (anyOf 1)integerAlternativeThe order number of the step that requires this dependency.
Format: int32
requiredByStepOrder (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
updatedAtstringRequired within parentThe date and time when this dependency was last updated, in ISO 8601 format.
Format: date-time
Retrieve sequence — sequences get By Sequence Id — response body — steps item
FieldTypePresenceDescription and constraints
$objectRoot
actionTypestringRequired within parentThe type of action to be performed in this step. Valid values include 'EMAIL', 'TASK', and 'FINISH_ENROLLMENT'.
Known values: ADAPTIVE_CONTAINER, EMAIL, FINISH_ENROLLMENT, TASK
createdAtstringRequired within parentThe date and time when this step was created, in ISO 8601 format.
Format: date-time
delayMillisJSONRequired within parent
delayMillis (anyOf 1)integerAlternativeThe delay before executing this step, specified in milliseconds as a 64-bit integer.
Format: int64
delayMillis (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
emailPatternModelOptionalExpand Update sequence — response body — steps item email Pattern
idstringRequired within parentThe unique identifier for this sequence step, represented as a string.
stepOrderJSONRequired within parent
stepOrder (anyOf 1)integerAlternativeAn integer indicating the order of this step within the sequence.
Format: int32
stepOrder (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
taskPatternModelOptionalExpand Retrieve sequence — sequences get By Sequence Id — response body — steps item task Pattern
updatedAtstringRequired within parentThe date and time when this step was last updated, in ISO 8601 format.
Format: date-time

Referenced models: Update sequence — response body — steps item email Pattern, Retrieve sequence — sequences get By Sequence Id — response body — steps item task Pattern

Update sequence — response body — steps item email Pattern
FieldTypePresenceDescription and constraints
$objectRoot
createdAtstringRequired within parentThe date and time when this email pattern was created, in ISO 8601 format.
Format: date-time
idstringRequired within parentThe unique identifier for this email pattern. It is a string.
templateIdstringRequired within parentThe identifier of the email template associated with this pattern. It is a string.
threadEmailToStepOrderJSONOptional
threadEmailToStepOrder (anyOf 1)integerAlternativeAn integer representing the order of the step to which this email pattern is threaded.
Format: int32
threadEmailToStepOrder (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
updatedAtstringRequired within parentThe date and time when this email pattern was last updated, in ISO 8601 format.
Format: date-time

SDK function policy ID: hubspot.sequences_get_by_sequence_id. Catalog operation: sequences_get_by_sequence_id. 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.read"]

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.