Sequence
Sequences are multi-step outreach cadences that send email and LinkedIn messages to enrolled contacts. A sequence is edited through its draft, published, then activated; contacts are enrolled into the published sequence. Start with Using sequences with the API for the lifecycle, the draft and version model, and a worked example.
Retrieve a sequence
Retrieve sequence performance
Retrieve a sequence enrollment
List sequence enrollments
List sequence messages
Retrieve a sequence message
Enroll and cancel contacts
Start a sequence test
Retrieve a sequence test
Activate a sequence
Deactivate a sequence
Retrieve a sequence draft
Update a sequence draft
Publish a sequence draft
List template variables
Discard a sequence draft
ModelsExpand Collapse
type SequenceActivateResponse struct{…}
Definition SequenceActivateResponseDefinitionPublished configuration, or null before the first publish.
Published configuration, or null before the first publish.
Pacing SequenceActivateResponseDefinitionPacingHow the whole sequence paces each step type it sends, keyed by sequence step type.
How the whole sequence paces each step type it sends, keyed by sequence step type.
Steps []SequenceActivateResponseDefinitionStepUnionEmail, LinkedIn and wait steps in execution order.
Email, LinkedIn and wait steps in execution order.
type SequenceActivateResponseDefinitionStepObject struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
type SequenceActivateResponseDefinitionStepObject2 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
Whether the connection request carries a note. A step authored before this setting existed reads as true.
type SequenceActivateResponseDefinitionStepObject3 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
Template SequenceActivateResponseDefinitionStepObject3TemplateThe email every contact receives.
The email every contact receives.
type SequenceActivateResponseDefinitionStepObject4 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
type SequenceActivateResponseDefinitionStepObject5 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
Whether the connection request carries a note. A step authored before this setting existed reads as true.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
Reviewers []SequenceActivateResponseReviewerExtra members who may approve this sequence’s FOR_REVIEW messages before they send. The sending member and the sequence’s creator always review, whether or not they are listed.
Extra members who may approve this sequence’s FOR_REVIEW messages before they send. The sending member and the sequence’s creator always review, whether or not they are listed.
Senders []SequenceActivateResponseSenderThe senders this sequence sends from; new contacts rotate across them. An archived sender stays listed but never sends; any change to the list drops it.
The senders this sequence sends from; new contacts rotate across them. An archived sender stays listed but never sends; any change to the list drops it.
type SequenceCreateResponse struct{…}
Definition SequenceCreateResponseDefinitionThe draft configuration, in the same shape as a published definition.
The draft configuration, in the same shape as a published definition.
Pacing SequenceCreateResponseDefinitionPacingHow the whole sequence paces each step type it sends, keyed by sequence step type.
How the whole sequence paces each step type it sends, keyed by sequence step type.
Steps []SequenceCreateResponseDefinitionStepUnionEmail, LinkedIn and wait steps in execution order.
Email, LinkedIn and wait steps in execution order.
type SequenceCreateResponseDefinitionStepObject struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
type SequenceCreateResponseDefinitionStepObject2 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
Whether the connection request carries a note. A step authored before this setting existed reads as true.
type SequenceCreateResponseDefinitionStepObject3 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
Template SequenceCreateResponseDefinitionStepObject3TemplateThe email every contact receives.
The email every contact receives.
type SequenceCreateResponseDefinitionStepObject4 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
type SequenceCreateResponseDefinitionStepObject5 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
Whether the connection request carries a note. A step authored before this setting existed reads as true.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
PublishWarnings []SequenceCreateResponsePublishWarningWhat publishing this draft would change for contacts already in the sequence; empty when nothing is affected. Before the first publish, the only possible warning is a proposed sender that was archived and would be left off.
What publishing this draft would change for contacts already in the sequence; empty when nothing is affected. Before the first publish, the only possible warning is a proposed sender that was archived and would be left off.
Code stringWhat publishing would change.
What publishing would change.
Reviewers []SequenceCreateResponseReviewerExtra members who may approve this sequence’s FOR_REVIEW messages before they send. The sending member and the sequence’s creator always review, whether or not they are listed.
Extra members who may approve this sequence’s FOR_REVIEW messages before they send. The sending member and the sequence’s creator always review, whether or not they are listed.
type SequenceDeactivateResponse struct{…}
Definition SequenceDeactivateResponseDefinitionPublished configuration, or null before the first publish.
Published configuration, or null before the first publish.
Pacing SequenceDeactivateResponseDefinitionPacingHow the whole sequence paces each step type it sends, keyed by sequence step type.
How the whole sequence paces each step type it sends, keyed by sequence step type.
Steps []SequenceDeactivateResponseDefinitionStepUnionEmail, LinkedIn and wait steps in execution order.
Email, LinkedIn and wait steps in execution order.
type SequenceDeactivateResponseDefinitionStepObject struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
type SequenceDeactivateResponseDefinitionStepObject2 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
Whether the connection request carries a note. A step authored before this setting existed reads as true.
type SequenceDeactivateResponseDefinitionStepObject3 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
Template SequenceDeactivateResponseDefinitionStepObject3TemplateThe email every contact receives.
The email every contact receives.
type SequenceDeactivateResponseDefinitionStepObject4 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
type SequenceDeactivateResponseDefinitionStepObject5 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
Whether the connection request carries a note. A step authored before this setting existed reads as true.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
Reviewers []SequenceDeactivateResponseReviewerExtra members who may approve this sequence’s FOR_REVIEW messages before they send. The sending member and the sequence’s creator always review, whether or not they are listed.
Extra members who may approve this sequence’s FOR_REVIEW messages before they send. The sending member and the sequence’s creator always review, whether or not they are listed.
Senders []SequenceDeactivateResponseSenderThe senders this sequence sends from; new contacts rotate across them. An archived sender stays listed but never sends; any change to the list drops it.
The senders this sequence sends from; new contacts rotate across them. An archived sender stays listed but never sends; any change to the list drops it.
type SequenceListEnrollmentsResponse struct{…}
Data []SequenceListEnrollmentsResponseData
ID of the step the contact is on, matching definition.steps; null when the contact has no current step the API returns.
Member ID of whoever enrolled the contact; null when they are no longer a member or the enrollment was automatic.
LastActivityKind stringThe latest activity on the enrollment. A reply or bounce that ended the enrollment is reported over a later open.
The latest activity on the enrollment. A reply or bounce that ended the enrollment is reported over a later open.
Estimated time of the next send, from the cadence, send window, pacing and sender; queue order and random gaps can push it later. Null while a message awaits review or is sending, while paused, or when it cannot be estimated.
Email and LinkedIn steps not yet sent, connection requests included.
Status stringACTIVE is progressing; AWAITING_REVIEW has a message waiting for approval; NEEDS_ATTENTION is held by a failed step, a held draft or an unavailable sender; PAUSED is stopped because the sequence is deactivated or it was paused in Lightfield. REPLIED, COMPLETED, CANCELLED and FAILED are final.
ACTIVE is progressing; AWAITING_REVIEW has a message waiting for approval; NEEDS_ATTENTION is held by a failed step, a held draft or an unavailable sender; PAUSED is stopped because the sequence is deactivated or it was paused in Lightfield. REPLIED, COMPLETED, CANCELLED and FAILED are final.
type SequenceListMessagesResponse struct{…}
Data []SequenceListMessagesResponseDataUnion
type SequenceListMessagesResponseDataOutboundMessage struct{…}
When the message was created, or when a reply was received. Lists sort by this field, newest first.
Reference SequenceListMessagesResponseDataOutboundMessageReferenceUnionThe email or LinkedIn message record behind this sequence message, readable with Retrieve an email or Retrieve a message under their own scopes; null when there is none.
The email or LinkedIn message record behind this sequence message, readable with Retrieve an email or Retrieve a message under their own scopes; null when there is none.
SequenceStepType stringType of that step.
Type of that step.
Status stringAWAITING_REVIEW is waiting for approval; SCHEDULED is composed and waiting for its send time; QUEUED is due and waiting on the sender. SENT, SKIPPED, FAILED and CANCELLED are final.
AWAITING_REVIEW is waiting for approval; SCHEDULED is composed and waiting for its send time; QUEUED is due and waiting on the sender. SENT, SKIPPED, FAILED and CANCELLED are final.
type SequenceListMessagesResponseDataReply struct{…}
When the message was created, or when a reply was received. Lists sort by this field, newest first.
Reference SequenceListMessagesResponseDataReplyReferenceUnionThe email or LinkedIn message record behind this sequence message, readable with Retrieve an email or Retrieve a message under their own scopes; null when there is none.
The email or LinkedIn message record behind this sequence message, readable with Retrieve an email or Retrieve a message under their own scopes; null when there is none.
SequenceStepType stringType of that step.
Type of that step.
type SequenceListResponse struct{…}
Data []SequenceListResponseData
Definition SequenceListResponseDataDefinitionPublished configuration, or null before the first publish.
Published configuration, or null before the first publish.
Pacing SequenceListResponseDataDefinitionPacingHow the whole sequence paces each step type it sends, keyed by sequence step type.
How the whole sequence paces each step type it sends, keyed by sequence step type.
Steps []SequenceListResponseDataDefinitionStepUnionEmail, LinkedIn and wait steps in execution order.
Email, LinkedIn and wait steps in execution order.
type SequenceListResponseDataDefinitionStepObject struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
type SequenceListResponseDataDefinitionStepObject2 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
Whether the connection request carries a note. A step authored before this setting existed reads as true.
type SequenceListResponseDataDefinitionStepObject3 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
Template SequenceListResponseDataDefinitionStepObject3TemplateThe email every contact receives.
The email every contact receives.
type SequenceListResponseDataDefinitionStepObject4 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
type SequenceListResponseDataDefinitionStepObject5 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
Whether the connection request carries a note. A step authored before this setting existed reads as true.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
Reviewers []SequenceListResponseDataReviewerExtra members who may approve this sequence’s FOR_REVIEW messages before they send. The sending member and the sequence’s creator always review, whether or not they are listed.
Extra members who may approve this sequence’s FOR_REVIEW messages before they send. The sending member and the sequence’s creator always review, whether or not they are listed.
Senders []SequenceListResponseDataSenderThe senders this sequence sends from; new contacts rotate across them. An archived sender stays listed but never sends; any change to the list drops it.
The senders this sequence sends from; new contacts rotate across them. An archived sender stays listed but never sends; any change to the list drops it.
type SequenceListTemplateVariablesResponse struct{…}
Data []SequenceListTemplateVariablesResponseData
Field SequenceListTemplateVariablesResponseDataFieldThe field the variable reads; null for built-in variables.
The field the variable reads; null for built-in variables.
ValueType stringType of the field.
Type of the field.
Group stringWhose value the variable prints: the enrolled contact, its first account, or the step’s sender.
Whose value the variable prints: the enrolled contact, its first account, or the step’s sender.
type SequencePublishDraftResponse struct{…}
Definition SequencePublishDraftResponseDefinitionPublished configuration, or null before the first publish.
Published configuration, or null before the first publish.
Pacing SequencePublishDraftResponseDefinitionPacingHow the whole sequence paces each step type it sends, keyed by sequence step type.
How the whole sequence paces each step type it sends, keyed by sequence step type.
Steps []SequencePublishDraftResponseDefinitionStepUnionEmail, LinkedIn and wait steps in execution order.
Email, LinkedIn and wait steps in execution order.
type SequencePublishDraftResponseDefinitionStepObject struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
type SequencePublishDraftResponseDefinitionStepObject2 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
Whether the connection request carries a note. A step authored before this setting existed reads as true.
type SequencePublishDraftResponseDefinitionStepObject3 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
Template SequencePublishDraftResponseDefinitionStepObject3TemplateThe email every contact receives.
The email every contact receives.
type SequencePublishDraftResponseDefinitionStepObject4 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
type SequencePublishDraftResponseDefinitionStepObject5 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
Whether the connection request carries a note. A step authored before this setting existed reads as true.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
Reviewers []SequencePublishDraftResponseReviewerExtra members who may approve this sequence’s FOR_REVIEW messages before they send. The sending member and the sequence’s creator always review, whether or not they are listed.
Extra members who may approve this sequence’s FOR_REVIEW messages before they send. The sending member and the sequence’s creator always review, whether or not they are listed.
Senders []SequencePublishDraftResponseSenderThe senders this sequence sends from; new contacts rotate across them. An archived sender stays listed but never sends; any change to the list drops it.
The senders this sequence sends from; new contacts rotate across them. An archived sender stays listed but never sends; any change to the list drops it.
type SequenceRetrieveDraftResponse struct{…}
Definition SequenceRetrieveDraftResponseDefinitionThe draft configuration, in the same shape as a published definition.
The draft configuration, in the same shape as a published definition.
Pacing SequenceRetrieveDraftResponseDefinitionPacingHow the whole sequence paces each step type it sends, keyed by sequence step type.
How the whole sequence paces each step type it sends, keyed by sequence step type.
Steps []SequenceRetrieveDraftResponseDefinitionStepUnionEmail, LinkedIn and wait steps in execution order.
Email, LinkedIn and wait steps in execution order.
type SequenceRetrieveDraftResponseDefinitionStepObject struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
type SequenceRetrieveDraftResponseDefinitionStepObject2 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
Whether the connection request carries a note. A step authored before this setting existed reads as true.
type SequenceRetrieveDraftResponseDefinitionStepObject3 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
Template SequenceRetrieveDraftResponseDefinitionStepObject3TemplateThe email every contact receives.
The email every contact receives.
type SequenceRetrieveDraftResponseDefinitionStepObject4 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
type SequenceRetrieveDraftResponseDefinitionStepObject5 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
Whether the connection request carries a note. A step authored before this setting existed reads as true.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
PublishWarnings []SequenceRetrieveDraftResponsePublishWarningWhat publishing this draft would change for contacts already in the sequence; empty when nothing is affected. Before the first publish, the only possible warning is a proposed sender that was archived and would be left off.
What publishing this draft would change for contacts already in the sequence; empty when nothing is affected. Before the first publish, the only possible warning is a proposed sender that was archived and would be left off.
Code stringWhat publishing would change.
What publishing would change.
Reviewers []SequenceRetrieveDraftResponseReviewerExtra members who may approve this sequence’s FOR_REVIEW messages before they send. The sending member and the sequence’s creator always review, whether or not they are listed.
Extra members who may approve this sequence’s FOR_REVIEW messages before they send. The sending member and the sequence’s creator always review, whether or not they are listed.
type SequenceRetrieveEnrollmentResponse struct{…}
ID of the step the contact is on, matching definition.steps; null when the contact has no current step the API returns.
Member ID of whoever enrolled the contact; null when they are no longer a member or the enrollment was automatic.
LastActivityKind SequenceRetrieveEnrollmentResponseLastActivityKindThe latest activity on the enrollment. A reply or bounce that ended the enrollment is reported over a later open.
The latest activity on the enrollment. A reply or bounce that ended the enrollment is reported over a later open.
Estimated time of the next send, from the cadence, send window, pacing and sender; queue order and random gaps can push it later. Null while a message awaits review or is sending, while paused, or when it cannot be estimated.
Email and LinkedIn steps not yet sent, connection requests included.
Status SequenceRetrieveEnrollmentResponseStatusACTIVE is progressing; AWAITING_REVIEW has a message waiting for approval; NEEDS_ATTENTION is held by a failed step, a held draft or an unavailable sender; PAUSED is stopped because the sequence is deactivated or it was paused in Lightfield. REPLIED, COMPLETED, CANCELLED and FAILED are final.
ACTIVE is progressing; AWAITING_REVIEW has a message waiting for approval; NEEDS_ATTENTION is held by a failed step, a held draft or an unavailable sender; PAUSED is stopped because the sequence is deactivated or it was paused in Lightfield. REPLIED, COMPLETED, CANCELLED and FAILED are final.
type SequenceRetrieveMessageResponseUnion interface{…}
type SequenceRetrieveMessageResponseOutboundMessage struct{…}
Content SequenceRetrieveMessageResponseOutboundMessageContentPlain-text content of the message. Null when the underlying record is no longer available; not included in list responses.
Plain-text content of the message. Null when the underlying record is no longer available; not included in list responses.
When the message was created, or when a reply was received. Lists sort by this field, newest first.
Reference SequenceRetrieveMessageResponseOutboundMessageReferenceUnionThe email or LinkedIn message record behind this sequence message, readable with Retrieve an email or Retrieve a message under their own scopes; null when there is none.
The email or LinkedIn message record behind this sequence message, readable with Retrieve an email or Retrieve a message under their own scopes; null when there is none.
SequenceStepType stringType of that step.
Type of that step.
Status stringAWAITING_REVIEW is waiting for approval; SCHEDULED is composed and waiting for its send time; QUEUED is due and waiting on the sender. SENT, SKIPPED, FAILED and CANCELLED are final.
AWAITING_REVIEW is waiting for approval; SCHEDULED is composed and waiting for its send time; QUEUED is due and waiting on the sender. SENT, SKIPPED, FAILED and CANCELLED are final.
type SequenceRetrieveMessageResponseReply struct{…}
Content SequenceRetrieveMessageResponseReplyContentPlain-text content of the message. Null when the underlying record is no longer available; not included in list responses.
Plain-text content of the message. Null when the underlying record is no longer available; not included in list responses.
When the message was created, or when a reply was received. Lists sort by this field, newest first.
Reference SequenceRetrieveMessageResponseReplyReferenceUnionThe email or LinkedIn message record behind this sequence message, readable with Retrieve an email or Retrieve a message under their own scopes; null when there is none.
The email or LinkedIn message record behind this sequence message, readable with Retrieve an email or Retrieve a message under their own scopes; null when there is none.
SequenceStepType stringType of that step.
Type of that step.
type SequenceRetrievePerformanceResponse struct{…}
ByStepType SequenceRetrievePerformanceResponseByStepTypeLifetime totals for each step type, across all of its steps.
Lifetime totals for each step type, across all of its steps.
Email SequenceRetrievePerformanceResponseByStepTypeEmailEmail steps.
Email steps.
LinkedinInvite SequenceRetrievePerformanceResponseByStepTypeLinkedinInviteLinkedIn connection request steps.
LinkedIn connection request steps.
LinkedinMessage SequenceRetrievePerformanceResponseByStepTypeLinkedinMessageLinkedIn message steps.
LinkedIn message steps.
PerStep []SequenceRetrievePerformanceResponsePerStepUnionPer-step statistics in published sequence order, including steps with no activity. Steps no longer in the published definition are included if they have sent messages.
Per-step statistics in published sequence order, including steps with no activity. Steps no longer in the published definition are included if they have sent messages.
type SequenceRetrievePerformanceResponsePerStepEmailStep struct{…}
type SequenceRetrievePerformanceResponsePerStepLinkedInMessageStep struct{…}
type SequenceRetrievePerformanceResponsePerStepLinkedInInviteStep struct{…}
Connection requests that were accepted.
Enrollments currently on this step, paused ones included.
type SequenceRetrieveResponse struct{…}
Definition SequenceRetrieveResponseDefinitionPublished configuration, or null before the first publish.
Published configuration, or null before the first publish.
Pacing SequenceRetrieveResponseDefinitionPacingHow the whole sequence paces each step type it sends, keyed by sequence step type.
How the whole sequence paces each step type it sends, keyed by sequence step type.
Steps []SequenceRetrieveResponseDefinitionStepUnionEmail, LinkedIn and wait steps in execution order.
Email, LinkedIn and wait steps in execution order.
type SequenceRetrieveResponseDefinitionStepObject struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
type SequenceRetrieveResponseDefinitionStepObject2 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
Whether the connection request carries a note. A step authored before this setting existed reads as true.
type SequenceRetrieveResponseDefinitionStepObject3 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
Template SequenceRetrieveResponseDefinitionStepObject3TemplateThe email every contact receives.
The email every contact receives.
type SequenceRetrieveResponseDefinitionStepObject4 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
type SequenceRetrieveResponseDefinitionStepObject5 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
Whether the connection request carries a note. A step authored before this setting existed reads as true.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
Reviewers []SequenceRetrieveResponseReviewerExtra members who may approve this sequence’s FOR_REVIEW messages before they send. The sending member and the sequence’s creator always review, whether or not they are listed.
Extra members who may approve this sequence’s FOR_REVIEW messages before they send. The sending member and the sequence’s creator always review, whether or not they are listed.
Senders []SequenceRetrieveResponseSenderThe senders this sequence sends from; new contacts rotate across them. An archived sender stays listed but never sends; any change to the list drops it.
The senders this sequence sends from; new contacts rotate across them. An archived sender stays listed but never sends; any change to the list drops it.
type SequenceRetrieveTestResponse struct{…}
Status SequenceRetrieveTestResponseStatusRUNNING until every step has finished, then COMPLETED, or FAILED when the test ended on a failure.
RUNNING until every step has finished, then COMPLETED, or FAILED when the test ended on a failure.
Steps []SequenceRetrieveTestResponseStepEvery step of the tested version that the Sequences API lists, in run order. Call steps are not part of the API yet, so a test reports nothing for them.
Every step of the tested version that the Sequences API lists, in run order. Call steps are not part of the API yet, so a test reports nothing for them.
Error SequenceRetrieveTestResponseStepErrorWhy the step failed; null unless outcome is FAILED.
Why the step failed; null unless outcome is FAILED.
Message SequenceRetrieveTestResponseStepMessageUnionThe composed message; null when the step has not composed one.
The composed message; null when the step has not composed one.
Outcome stringPENDING while the step has not run, including a step a finished test never reached, COMPOSED when it produced a message, SKIPPED when it produced nothing: a test never waits, so a wait is always SKIPPED, and a send step is SKIPPED when it has nothing to send, such as a LinkedIn invite another step already sent. FAILED when it failed: see error.
PENDING while the step has not run, including a step a finished test never reached, COMPOSED when it produced a message, SKIPPED when it produced nothing: a test never waits, so a wait is always SKIPPED, and a send step is SKIPPED when it has nothing to send, such as a LinkedIn invite another step already sent. FAILED when it failed: see error.
type SequenceUpdateDraftResponse struct{…}
Definition SequenceUpdateDraftResponseDefinitionThe draft configuration, in the same shape as a published definition.
The draft configuration, in the same shape as a published definition.
Pacing SequenceUpdateDraftResponseDefinitionPacingHow the whole sequence paces each step type it sends, keyed by sequence step type.
How the whole sequence paces each step type it sends, keyed by sequence step type.
Steps []SequenceUpdateDraftResponseDefinitionStepUnionEmail, LinkedIn and wait steps in execution order.
Email, LinkedIn and wait steps in execution order.
type SequenceUpdateDraftResponseDefinitionStepObject struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
type SequenceUpdateDraftResponseDefinitionStepObject2 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
Whether the connection request carries a note. A step authored before this setting existed reads as true.
type SequenceUpdateDraftResponseDefinitionStepObject3 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
Template SequenceUpdateDraftResponseDefinitionStepObject3TemplateThe email every contact receives.
The email every contact receives.
type SequenceUpdateDraftResponseDefinitionStepObject4 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
type SequenceUpdateDraftResponseDefinitionStepObject5 struct{…}
DeliveryMode stringAUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
AUTO sends without manual approval, subject to the send window and limits; FOR_REVIEW requires a person to approve the draft before sending.
Whether the connection request carries a note. A step authored before this setting existed reads as true.
How each message is written: AGENT composes it from prompt; TEMPLATE sends template to every contact, with its variables filled in.
PublishWarnings []SequenceUpdateDraftResponsePublishWarningWhat publishing this draft would change for contacts already in the sequence; empty when nothing is affected. Before the first publish, the only possible warning is a proposed sender that was archived and would be left off.
What publishing this draft would change for contacts already in the sequence; empty when nothing is affected. Before the first publish, the only possible warning is a proposed sender that was archived and would be left off.
Code stringWhat publishing would change.
What publishing would change.
Reviewers []SequenceUpdateDraftResponseReviewerExtra members who may approve this sequence’s FOR_REVIEW messages before they send. The sending member and the sequence’s creator always review, whether or not they are listed.
Extra members who may approve this sequence’s FOR_REVIEW messages before they send. The sending member and the sequence’s creator always review, whether or not they are listed.
type SequenceUpdateEnrollmentsResponse struct{…}
Results []SequenceUpdateEnrollmentsResponseResultUnionOne result per distinct contact, additions first, then removals.
One result per distinct contact, additions first, then removals.
type SequenceUpdateEnrollmentsResponseResultEnrollmentChanged struct{…}
Outcome stringenrolled created the enrollment, already_enrolled left an open one as is, unenrolled cancelled it.
enrolled created the enrollment, already_enrolled left an open one as is, unenrolled cancelled it.