mcpDeterministic

Update subsequence

tools/call

Update an existing subsequence on a campaign (e.g. toggle enabled, change the workflow, or retarget the trigger). Changing the trigger is rejected if it collides with another subsequence on the same campaign.

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.

subsequenceIdrequired

string

No description.

trigger

string

No description.

interested_reply | meeting_request | no_reply | custom_tag

triggerTag

string

No description.

name

string

No description.

enabled

boolean

No description.

triggerConfig

object

No description.

workflowDefinition

object

No description.

Example

MCP tools/calljson

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

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.