End

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

1. Open the workflow and click + where the run should stop.
2. Pick End. There is nothing to configure.
3. Save the step, then publish the workflow.

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 lane the End step 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, so a segment that decides the conversation is finished does not have to be the last thing on every lane 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, so an End step cannot be reached afterward in that same run — only in whatever runs later, after the wait fires.)
• 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.

Related

• Jump To — Send the run straight to another step already on the canvas, forward or backward, capped by a per-step limit so a deliberate loop cannot run forever.
• Condition — Split the run into up to twelve lanes plus a None lane, checked top to bottom — the first lane whose conditions all pass wins, and Condition tests one field against one value at a time.
• 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.
• Workflows: how a flow runs — A workflow is one trigger, optional conditions and an ordered list of steps; only a published workflow runs, and this article explains how a run starts, forks, pauses, fails and stops.