Trigger workflow
campaignstack_trigger_workflowConfirmed consequential execution: adds the selected leads to a workflow, or with no leadIds runs its sourcing now. A lead enters a workflow once: leads already in it, in any status, and leads an exclusion matches are skipped and counted in skipped. It joins the workflow queue and obeys pacing, review, account, and safety limits. To retry failed entries, use campaignstack_retry_workflow_entries.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"workflowId": "<workflowId>",
"confirmed": "<confirmed>"
},
"name": "campaignstack_trigger_workflow"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| leadIds | No | ||
| confirmed | Yes | Confirms this starts workflow execution for real leads. | |
| workflowId | Yes | ||
| workspaceId | No | Workspace ID. Omit it when this connection reaches one workspace: a workspace key (cs_) is bound to its own, and a user key (csu_) or connected app whose person belongs to exactly one workspace defaults to that one. Required only when the person belongs to several; the error then lists them, and campaignstack_whoami reports them too. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ok | No | ||
| results | No | ||
| warnings | No | ||
| workflowId | No | ||
| workspaceId | No |