Remove from Workflow
Cancel this conversation's pending waits — the step that stops a reminder chase the moment the contact replies or pays, before the next one is due.
Quick start
- Go to Automate → Workflows and open a workflow. Click + and pick Remove from Workflow.
- Put it in a workflow that starts when the customer replies or pays, for example Message Received or Order Paid.
- Choose which workflow's pending waits to cancel: All workflows, or one named workflow.
- It only cancels waits already queued — a step running right now still finishes.
- Set Status to Published in the top toolbar, Save, confirm Publish. Agents: ask an owner or admin.
Watch out
- Despite the name, it does not stop a workflow running right now — only already-queued waits are cancelled.
- End stops only the run it sits in — it cannot stop another workflow; cancelling that one's queued waits is this step's job.



Details
Getting here
Automate → Workflows, open a workflow, click + on the canvas, then pick Remove from Workflow under Add Steps.
Before you start
- An owner, admin or agent can add this step and save the workflow. Publishing it is an owner or admin action.
- Building and running workflows depends on your plan; see pricing.
- Nothing outside Inchat has to be connected. The step only cancels rows already queued for this conversation.
Set up
- Open the workflow and click + where the cancellation belongs — typically right after the event that makes the chase unnecessary, such as a reply or a payment.
- Pick Remove from Workflow.
- Choose which workflow's pending waits to cancel — All workflows, or one named workflow.
- Save the step. To publish: set Status to Published in the toolbar at the top of the editor, click Save, then confirm with Publish. The dropdown on its own changes nothing until you save.
Fields
- Workflow to cancel
- Which workflow's queued waits this step cancels for the conversation. Use the dropdown in the step — it has no visible label on screen, only one read by a screen reader.
- Default: All workflows
- Limits: The list never offers this same workflow as a choice, so a stored value that matches neither a listed workflow nor All workflows — for example, a deleted workflow — falls back to showing This workflow.
How it works
- The step cancels every still-pending queued row for this conversation — either across the whole workspace's workflows, or only the one workflow chosen.
- Cancelled rows are marked so the check that clears the queue skips them.
- That covers a Wait step's own pause and an Assign To step's Timeout Branch message (the delayed message it sends if nobody answers) — both wait in the same queue underneath.
- All workflows can also cancel a reply the AI had delayed because of sending limits.
- A wait that has already fired and moved on cannot be cancelled after the fact — only rows still waiting for their due time are affected.
- The This workflow label does not change what gets cancelled — the step still cancels waits queued against whichever workflow id was originally stored.
- That is this workflow's own id if that is what was picked, or a since-deleted workflow's id if that is what remains.
When it fails
- There is nothing to cancel: the step still succeeds — an empty result is not a failure, it just means no matching wait was pending.
Limits
- Despite the name, it does not stop a workflow that is actively running on this conversation right this moment — a step already executing finishes; only what has already been queued for later is affected.
- It cannot release a contact stuck waiting for an answer to an Ask a Question step in some other workflow — that is a different kind of pending state, not a queued wait.
- It cannot cancel a workflow that has been triggered but has not yet started running — queued but not yet processed — it only reaches waits that are already queued and pending.
- It does not touch anything about the AI, the assignee or the conversation's status — cancelling a queued Timeout Branch message, for instance, does not undo the assignment that queued it.
- All workflows is genuinely all of them — including a rate-limit retry the AI's own auto-reply queued, which has no workflow behind it at all.
- There is no way to cancel only a workflow's own queued rows while leaving those retries alone.
Use cases
- A payment-reminder workflow queues a chase every day the invoice stays open; the moment the customer pays, this step cancels the rest of the chase.
- A workflow sets a short reply-timeout on an Assign To step; if the assignee replies before the timeout, a later workflow step cancels that queued timeout message so it never goes out.
FAQ and troubleshooting
- Does this stop a workflow that is running right now?
- No. It only cancels waits that are already queued for later — a step actively running when this fires finishes on its own.
- Will this release a contact stuck waiting on a question from another workflow?
- No. A parked question is a different kind of pending state; Remove from Workflow only cancels queued waits.
Reading this with an AI assistant? Plain Markdown version.