Skip to main content
POST
Add Dynamic Action

Authorizations

X-API-Key
string
header
required

Body

application/json
action
object
required

Action to add. Select exactly one typed variant. email requires prompt; linkedin_message and call_task require message; linkedin_inmail requires prompt and subject; manual_task requires name. Every variant requires assignedUserId.

contact
object | null

Optional verified contact context, normally forwarded from find_contact_data or a customer-requested enrichment result in this conversation.

  • All fields are optional.
  • On an existing enrollment, prospectId, email, linkedInUrl, and phone may only fill blanks and reject conflicts; firstName, lastName, role, and location only fill missing properties.
  • Do not use this tool to enrich missing data.
company
object | null

Optional verified company context related to contact.

  • All fields are optional.
  • It is stored as enrollment context only and does not prove that the contact works for this company.
  • On an existing enrollment, every company field only fills a missing property and never overwrites an existing value.
enrollmentId
string | null

Optional existing MCP Dynamic Actions enrollment/activity id to extend.

  • Use the exact enrollmentId returned by find_mcp_enrollment for the customer-selected candidate.
  • If the selected enrollment lacks firstName or lastName, also pass both names in contact before appending an action.
  • If find_mcp_enrollment returned any candidates, do not choose this value or omit it until the customer explicitly decides whether to continue one of those enrollments or start a new sequence.
  • Omit when no MCP enrollment candidate was found to create a new enrollment; when the original request already specifies the action and all required identity data, do this without asking the customer to confirm the same action again.
ownerId
string | null

Optional default owner user id for the dynamic enrollment.

  • Use the exact current userId from get_current_user or a userId returned by list_team_members.
  • Omit to keep the existing owner when extending an enrollment, or use the current MCP user for a new enrollment.
priority
integer | null

Optional scheduling priority for the whole dynamic enrollment.

  • Use 1 for High, 0 or omit for normal, and -1 for Low.
  • Higher values are preferred first.
  • Omit for priority 0 on a new enrollment or to preserve priority when extending an existing enrollment.
  • When supplied with enrollmentId, this updates the selected enrollment priority.
sourceDescription
string | null

Optional UI context for the dynamic enrollment, limited to 500 characters.

  • When useful context is known, write one to three concise sentences describing how this contact came to the sender and their relevant relationship; do not invent facts or merely repeat the action.
  • Omit when no useful context is known, which preserves the existing description when extending an enrollment.
  • Supplying a value for an existing enrollment replaces its prior sourceDescription.
allowUnreadyLinkedInAccount
boolean | null

Allow creating a LinkedIn action, or appending a follow-up to a LinkedIn connection outcome branch, even when the assigned team member's LinkedIn account is missing, disconnected, not alive, relations sync is incomplete, or the existing connection action is failed/canceled due account readiness.

  • Use only after the customer explicitly asks to create the action despite LinkedIn account readiness problems.
  • Social actions permission and contact.linkedInUrl are still required for LinkedIn actions.
  • For InMail, an already connected account must still have an eligible Premium or Sales Navigator plan; this flag only permits authoring before account readiness is available.

Response

Tool result.