mcpDeterministic

Create subsequence

tools/call

Create a follow-up subsequence on a campaign for a given trigger type. Only one subsequence per trigger (or per custom tag) is allowed per campaign. Omit workflowDefinition to use the system default single-step workflow for the trigger.

Parameters

workspaceId

string

Optional workspace ID or slug. Required when this credential can access multiple workspaces and no workspace was configured on the client.

campaignIdrequired

string

No description.

triggerrequired

string

What causes this subsequence to fire.

interested_reply | meeting_request | no_reply | custom_tag

triggerTag

string

Required when trigger is custom_tag. The inbox tag name that fires this subsequence. Cannot be a built-in pipeline tag.

name

string

No description.

enabled

boolean

Defaults to false (disabled) unless set.

triggerConfig

object

e.g. { noReplyDays: 3 } for the no_reply trigger.

workflowDefinition

object

ReactFlow-style { nodes, edges } graph of message steps with delays. Omit to use the default workflow for the trigger type.

Example

MCP tools/calljson

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "create-subsequence",
    "arguments": {
      "campaignId": "00000000-0000-4000-8000-000000000000",
      "trigger": "interested_reply"
    }
  }
}

Response

The operation is available, but its typed response schema has not been published yet.

JSON-RPC errors

-32602: Invalid parameters. Field-level details are returned in the JSON-RPC error data.
-32001: Authentication or hosted AI consent is required.
-32003: Workspace access is denied.
-32029: The request was rate limited.