Short answer: You can cancel workflow in CircleCI by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the CircleCI Cancel Workflow action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Workflow ID workflow_id | string | Required | Workflow ID. Example: wf-abc-123 |
{"workflow_id": "e.g. wf-abc-123"}
{"message": "Accepted."}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.