Skip to main content
POST
Create Contact Sequence

Authorizations

X-API-Key
string
header
required

Body

application/json
action
object
required

Exactly one action: email, linkedin_connect, linkedin_message, linkedin_inmail, linkedin_profile_view, manual_task, or call_task.

  • Use the matching typed payload.
  • Email requires final prompt content and a subject for a new thread; LinkedIn InMail requires prompt and subject.
  • Call and manual tasks require assignedUserId.
  • Email uses emailAccountId, not assignedUserId.
  • Approval defaults to enabled.
  • A delay uses hh:mm:ss or d.hh:mm:ss; follow-up emails and LinkedIn chat actions enforce their remaining three-hour gap.
  • The first action uses the default append target; connection outcome branches require an existing connection action.
contact
object | null

Verified contact identity and context. Provide prospectId resolving to a full name, or firstName and lastName with email, linkedInUrl, phone, or company.domain. Forward known verified fields; do not enrich automatically.

company
object | null

Optional verified company context for this contact. It does not prove employment.

ownerId
string | null

Creation-only permanent enrollment owner; defaults to the current user. Members can select only themselves; admins can select an active team member.

priority
integer | null

Scheduling priority for the new enrollment: 1 High, 0 normal (default), -1 Low.

sourceDescription
string | null

Optional known relationship or origin context, up to 500 characters. Do not invent facts.

allowUnreadyLinkedInAccount
boolean | null

Allow authoring a LinkedIn action despite account readiness problems only after the customer explicitly requests it. Does not bypass Social permission, contact URL, or runtime readiness and plan checks.

allowExcludedContact
boolean | null

Omit or set false on the first attempt. Set true only after an exclusion rejection and explicit customer confirmation to bypass it for this call. Does not remove exclusions.

Response

Tool result.