End
Stop the workflow here for this contact, even when End is inside a Condition or Date & Time path.
Quick start
- Go to Automate → Workflows and open a workflow. Click + and pick End.
- There is nothing to configure — reaching it stops the whole run, not just this path.
- Set Status to Published in the top toolbar, Save, confirm Publish. Agents: ask an owner or admin.
Watch out
- End does not cancel anything already queued — for example, a delayed message an earlier Assign To step queued still goes out on schedule.
- End does not close the conversation or change who it is assigned to.



Details
Getting here
Automate → Workflows, open a workflow, click + on the canvas, then pick End 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, and there is nothing to configure — End takes no fields.
Set up
- Open the workflow and click + where the run should stop.
- Pick End. There is nothing to configure.
- 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.
How it works
- Reaching an End step stops the run there: no later step in the workflow executes for this contact on this run, not just the rest of the path it sits on.
- That reach is deliberate — an End step placed inside a Condition branch or a Date & Time branch stops the whole run, not only that branch.
- A step that decides the conversation is finished does not have to be the last thing on every path for that to hold.
When it fails
- End cannot fail on its own — it takes no fields and makes no lookup, so reaching it always stops the run. The surprise operators report instead is what does not also stop: see Limits.
Limits
- It does not cancel anything this run already queued for later.
- A Timeout Branch message an earlier Assign To step queued still fires on schedule, even though the run that queued it later reached End.
- Cancelling it is Remove from Workflow's job, not End's.
- A Wait step earlier in the same run is not an example of this: reaching a Wait suspends the run into a queued continuation right there.
- If an earlier Wait is still counting down, End has not been reached yet; the workflow carries on when the wait finishes.
- It sends the customer nothing and changes nothing about the conversation's assignee or status by itself — it only stops the run.
Best practices
- Use End when a path is genuinely finished and nothing after it should run, even in a branch further out on the canvas.
- Reach for Remove from Workflow as well if the run also queued something that needs cancelling.
Use cases
- A self-serve path resolves the customer's request and ends there, without falling through to a follow-up meant for unresolved conversations.
- A Condition step's branch for "already handled" ends the run immediately, while the other branches continue with the rest of the workflow.
Reading this with an AI assistant? Plain Markdown version.