Test and publish a workflow

Try a workflow on a pretend conversation without sending anything, then publish it — and know what Publish refuses, warns about, and locks.

Quick start

  1. Go to Automate → Workflows, open a workflow, click Save — the test only sees the saved version — then open Test.
  2. Pick the Channel, add values for your conditions under More fields, then click Run test. Missing ones show (not set).
  3. Fix anything listed under Check before publishing.
  4. Set Status to Published in the top toolbar, Save, confirm Publish. Agents: ask an owner or admin.
  5. Or click the coloured Draft / Published / Stopped label on the workflows list.

Watch out

  • WhatsApp only allows a free-form message within 24 hours of the customer's last message — a warning does not stop publishing, but the send can fail.
Status set to Published, next to Save — the top toolbar's publish control.
The confirm dialog: this starts running on live conversations as soon as you save.
Details

Getting here

Automate → Workflows, open a workflow, then the Test tab under the canvas. To publish, set Status to Published in the editor and press Save, or click the status chip on the workflows list.

Before you start

  • An owner, admin or agent can open the Test tab, build a workflow and save it as a draft. Publishing is an owner or admin action everywhere it can be done — the status chip on the list refuses it, and a save from the editor, to anyone else.
  • Stopping a Published workflow from the chip is owner or admin only. From inside the editor, an agent can do it too, by changing Status to Stopped and pressing Save — the editor's save does not check role for that particular move, only for reaching Published.
  • Incoming Webhook workflows are different: only an owner or admin can save them, at any status — because saving one is what issues, or keeps, the webhook's URL.
  • Building and publishing workflows depends on your plan; see pricing. Some plans also cap how many workflows can be Published at once.
  • Nothing outside Inchat has to be connected to test. Publishing a workflow whose trigger depends on a connected account does need it (see When it fails).

Set up

  1. Build the workflow and press Save. The test reads the saved workflow, not what is on the canvas, so an unsaved edit is not in it.
  2. Click Test under the canvas. The panel is closed until you do.
  3. Pick the Channel the message would arrive on: WhatsApp, Messenger, Instagram or Website widget. Optionally paste a conversation id under Conversation (optional) to borrow that conversation's real channel and ad referral.
  4. Under More fields, type a value for the condition to check, in this form: {"message":{"text":"price"}}. Change price to your own words. If it is not valid JSON, Run test shows Context fields must be valid JSON.
  5. Click Run test. Read the headline, the Conditions list (each rule, what it expected, and what the test actually held) and the numbered steps.
  6. If the plan reaches an Ask a Question step it stops at Waiting for the customer. Pick an answer, No reply, or Replies that match no option to see what runs next. Undo last answer goes back one; Start over restarts.
  7. Fix anything listed under Check before publishing.
  8. To publish from the editor, set Status to Published and press Save, read the Confirm publishing box (it lists any WhatsApp timing warnings), then press Publish. From the workflows list, click the status chip instead: it cycles Draft → Published → Stopped → Draft.

How it works

  • Run test plans the path; it does not run the workflow. It sends no message, writes nothing and queues no wait — it reads the saved workflow and prints what would happen.
  • It works on a Draft or Stopped workflow as well as a Published one. For those the headline reads Would not run live (draft/stopped), followed by how many steps it would run if published.
  • The test judges the trigger's own limits first — its channel, entry source and ad — and then the top-level conditions, one line each: what the rule expects and what the test's context actually held.
  • The test's context is thin: the Channel you pick and, if you paste a conversation id, that conversation's channel and ad referral. A condition on anything else — a tag, the message text, a contact field — shows (not set) unless you type a value into More fields.
  • At a Condition, Branch or Date & Time (business hours) step the test follows the first path that matches. Date & Time is judged against the clock at the moment you press Run test, not when a real customer would reach it.
  • At a Randomizer (A/B split) step — its own button reads + Add lane — the test picks a path by the same weights, and the same conversation always lands on the same path. The test may show a different path from the one a real customer gets — a live run picks independently. Without a pasted conversation id, every test takes the same path unless you type a contact id into More fields.
  • At Ask a Question the test stops and waits for you. Each option becomes a button, plus No reply (times out after …), Replies that match no option when the question has options, and a text box for a question that accepts typed answers. Each pick continues down the Success, Timeout or Invalid path.
  • A Wait is not waited. The test adds its length to a running delay and marks the steps after it, for example [delayed +30s] — this step would happen 30 seconds later. An End step stops the plan, the way it stops a live run.
  • Check before publishing lists problems found on the whole flow, not only the path the test walked. At the moment it checks one thing: a question whose answer leads to no step, so the run simply ends and the answer is never used.
  • Only a Published workflow starts from a real event, and its trigger and conditions still have to match that event.
  • Publishing is refused unless your plan allows workflows, and unless it would not take you past your plan's cap on Published workflows.
  • Three triggers need a connected channel or account before they may be published. Click-to-Chat Ads needs a WhatsApp, Messenger or Instagram channel. TikTok Messaging Ads needs a connected TikTok ads account, and Call Ended needs a WhatsApp channel. A draft may be built before it is connected.
  • A Trigger Another Workflow step that names a workflow is checked at publish: that workflow must exist, must be Published, and must not hand back to this one. Only the first problem found is shown.
  • A Message Received trigger with no channel picked and no condition is refused, so a workflow cannot be published to answer every inbound message by accident.
  • WhatsApp timing warnings never block anything. Inchat adds up the waits and question timeouts in your flow to see whether a free-form message could be sent more than 24 hours after the customer last wrote.
  • It flags any free-form step that can be reached that late.
  • A free-form step is Send a Message, Send a File (voice / image / video), Ask a Question, AI Reply, Request WhatsApp Contact Info, Ask for Marketing Consent or Send Products (WhatsApp catalog).
  • In the editor the warnings show as a clock badge in the toolbar with a count, and again in the Confirm publishing box, which says you can publish anyway. On the workflows list, clicking the chip opens the same warning with a Publish anyway button. If the list cannot read the warnings, the publish goes ahead as if there were none.
  • A Send WhatsApp Template step does not reset that clock in the simulation; a customer replying to a question does.
  • The Confirm publishing box also warns when a step does the same job as an AI agent action in this workspace, for example both set the lifecycle stage or tag the contact. It names the step and suggests who should own it.
  • That warning is only a warning, like the WhatsApp timing one. You can publish anyway.
  • A Published workflow opens read-only, and you do not have to stop it to change it. Press Edit, make your changes and press Save draft.
  • The changes are kept beside the published version. Customers keep getting the published one until you press Publish changes; Discard changes throws the changes away.
  • Saving, publishing and discarding changes on a published workflow are owner or admin actions. Other roles are not offered Edit on one, and see the published version.
  • Publishing changes does not cut anyone off. A conversation already waiting on a Wait step or on a question finishes on the version it started with.
  • Set exit conditions is the exception. The exit conditions you publish apply at once, to conversations already inside the workflow as well.
  • Removing an Ask for Marketing Consent step has the same reach. A customer still answering it is then treated as any incoming message, and leaves if the workflow exits on one.
  • A conversation that starts after you publish gets the new steps. The Confirm publishing changes box says how many are waiting on a timer and how many on an answer.
  • While a workflow has unpublished changes, the workflows list shows Unpublished changes beside its name and the editor opens on the changes. View published version shows what customers are getting.
  • Two controls on that screen do not wait for Publish changes. Show in Send a flow applies as soon as you change it, and Update the shared rule is switched off until the changes are published.
  • Show performance is off while the changes are on the canvas, because its numbers are counted on the published version.
  • On a published workflow with unpublished changes, the Test tab plans the changes as last saved and says so: Testing your unpublished changes, as last saved.
  • Stopping a workflow keeps its unpublished changes. Publishing it again, from the workflows list or the editor, puts the last published version back, not the changes.
  • A stopped workflow that still holds changes opens on its last published steps, read-only, and the workflows list shows Changes waiting · not live beside it.
  • An owner or admin presses Apply changes to make them the workflow's steps, or Discard changes. Applying does not publish: the workflow stays stopped.
  • Stopping cancels that workflow's queued Wait steps. A conversation in the middle of one of its questions keeps the question it was shown and can still answer it.
  • You can abandon them instead: tick Abandon them instead when stopping in the editor, or click Stop and abandon them on the workflows list. They get nothing further, and each thread is tagged and noted for a person.
  • When other published workflows hand off to the one you are stopping BY PICKING IT FROM THE LIST, the stop shows their names first. It warns; it does not refuse.
  • A hand-off written by a prebuilt template or the AI builder can name the target workflow instead of picking it from the list. That kind of hand-off is not found by this check and is not shown here — it will still fail the same way once you stop the target.

When it fails

  • Save is refused in the editor before any publish check, in three cases.
  • No trigger is chosen: Select a trigger to start this workflow.
  • A step still has a configuration error: Fix N configuration error(s) before saving.
  • There is no step at all: Add at least one step (click + on the canvas).
  • Publish refused, wrong role: the status chip says Only owners and admins can publish or stop automations., and a save to Published from the editor says Only owners and admins can publish automations. The workflow keeps its status.
  • Publish refused, plan: Workflows need a paid plan. Start a plan under Settings → Billing to build one.
  • Publish refused, over the cap: This plan keeps N live workflows. Stop one, or talk to us under Settings → Support to move to a bigger plan. Nothing changes until one workflow is stopped or the plan is changed; see pricing.
  • Publish refused, trigger not connected: the message names the missing account, for example No TikTok ads account connected., and the workflow stays as it was.
  • Publish refused, hand-off target: a Trigger Another Workflow step points at a workflow that no longer exists, is itself, or hands straight back (the two would loop).
  • Or the target is not published: “name” is draft — publish it before you publish this workflow.
  • Publish refused, unscoped trigger: This workflow runs on every inbound message in the workspace. Add at least one condition (for example “Message sender is customer” plus a keyword or a channel) before publishing.
  • Saving a published Contact Inactive workflow FROM THE EDITOR is refused while it holds a free-form step: Published inactivity workflows can only contact customers with approved WhatsApp templates. Replace free-form message, media, question, AI reply, or quote steps with Send Template. The workflows list's status chip does not run this check — a Contact Inactive draft holding a free-form step can be published straight from the chip.
  • Publish changes runs the publish checks above on your changes. When one refuses, the reason appears in the editor's error line, the published version keeps running, and your changes stay saved.
  • A tab left open from before may still try to save over a published workflow. That save is refused: Published workflows are locked. Reload this page and press Edit to change it without stopping it.
  • A refusal appears in red beside the chip or in the editor's error line, and the workflow's status does not change.
  • After a workflow is published, a Trigger Another Workflow target can still be stopped or deleted. The publish check does not run again.
  • When a customer reaches that step, it is recorded as failed and the customer gets nothing from the hand-off. Its line in the run log reads that workflow is stopped, so it cannot be entered (or that workflow no longer exists). Steps placed after it in the entry workflow still run.
  • A hand-off chosen by workflow name (written this way by a prebuilt template or the AI builder), rather than picked from the list, is not checked at publish. When it runs with no published workflow of that name, the step fails with no published workflow named “…” — the funnel step it hands to is missing.
  • A free-form send that meets a closed messaging window when the workflow really runs fails that step with Messaging window closed — free-form send blocked. Use a send_template step (approved WhatsApp / utility template) instead.
  • You read the reason for a failed step in the workflow's Activity tab: pick the run under Execution log.

Limits

  • A test sends nothing, so it cannot show that a template is approved or that the contact has given marketing consent — those are checked only when a Send WhatsApp Template step really sends.
  • An HTTP Request, Add Google Sheets Row or AI Reply step appears as one summary line. The test does not call the address, reach the sheet or write the reply, so it cannot show whether any of them works.
  • The test follows one path per run. The paths it did not take are not shown, and a Trigger Another Workflow step appears as a line only: the test does not enter the workflow it names.
  • The test judges only the trigger's channel, entry-source and ad limits. Other trigger settings, such as inactivity minutes, are not simulated.
  • The test does not check WhatsApp's 24-hour window. It cannot know when a real customer last wrote, and the timing warnings belong to the editor and the publish box, not to the test.
  • The timing warnings look at steps and the trigger only. They do not know which channel a conversation will arrive on, and they cost a clock-time wait as a full day, so they can warn where a send would in fact arrive in time.
  • Publishing checks only what this article lists. It does not look up the teammate, tag, template or contact field a step names.
  • It also does not check the accounts that Add Google Sheets Row and Send Conversions API Event need — a step that needs one is found out when it runs.
  • Stopping a workflow cancels only that workflow's own queued waits. It does not touch another workflow's waits, even one that hands off to it.
  • The test and Publish cannot prove a workflow will answer a real customer. They show the path and the checks above, not whether the trigger's event will happen, a provider will accept a send, or a customer will reply.

Best practices

  • Test each path on purpose. Put a value into More fields for the condition that decides it, run the test, then change the value and run it again.
  • Publish the workflow another one hands to first, then the workflows that hand off to it. Publishing in the other order is refused.
  • Before you stop a workflow that others hand off to, read the names the stop box shows.
  • The stop box only lists hand-offs picked from the workflow list, not ones that name the target by typed text. Every workflow that hands off to it, listed or not, fails at that step until you publish it again.
  • When a timing warning names a step, put Send WhatsApp Template in its place or shorten the wait before it. A template is the send that may go out after the window closes.
  • Save before you test. The test only ever sees the last saved version.

Use cases

  • Before switching on Aurelia Skincare's welcome flow, test it on WhatsApp with {"message":{"text":"price"}} and again with other text, and check each condition line says what you meant.
  • Sarah Chen answers a qualifying question with a button: pick that option in the test, then No reply, then Replies that match no option, to see all three paths before any customer meets them.
  • A main flow and three entry flows for Michael Torres's ad campaigns: publish the main flow first, then each entry flow.
  • A nurture flow that waits two days between messages: the publish box warns about the later message; swap it for Send WhatsApp Template, then publish.

FAQ and troubleshooting

Does Run test send a real message to my customer?
No. It sends nothing, writes no tag or note, saves nothing and queues no wait. It prints the steps the workflow would take.
Can I test a workflow that is still a Draft?
Yes. The headline says Would not run live (draft/stopped) and gives the number of steps it would run if published.
The test says it would not run. Why?
Open the Trigger scope box if there is one: the channel, entry source or ad you chose is outside the trigger's limits. Otherwise read the Conditions list — each failed rule shows what it expected and what the test actually held. (not set) means the test had no value for that field; paste a conversation id or type the value under More fields.
Will the Randomizer test tell me which variant a customer gets?
No. It shows that the path exists and what follows it. The same conversation always lands on the same path in a test, and that is not the path a live contact will get.
Publishing was refused. What do I check?
Read the red message. It names one of the refusals listed under When it fails: your role, your plan, or the cap on Published workflows. It could also be a missing connected account, a Trigger Another Workflow target that is missing, not published or hands back, or a Message Received trigger with no channel and no condition. From the editor, it could instead be a free-form step in a Contact Inactive workflow. Fix that one, then publish again.
Publishing warned me about WhatsApp's window. Did it block?
No. The box says you can publish anyway, and Publish anyway does. The warning means a free-form message placed after a long wait may be refused by WhatsApp; use Send WhatsApp Template or shorten the wait.
I need to change a workflow that is Published.
You do not have to stop it. An owner or admin presses Edit, makes the changes, presses Save draft and then Publish changes. Customers keep getting the published version until then, and a conversation already waiting inside the workflow finishes on the steps it started with. Stopping it to edit still works, but stopping cancels its queued waits. Publishing again after a stop needs an owner or admin, even if an agent was the one who stopped it.
A workflow handed off to a workflow I later stopped. What happens?
Nothing stops you from stopping it. The entry workflow keeps running, the Trigger Another Workflow step fails with its reason in the Execution log, and the customer gets nothing from the hand-off. Publish the target again, if it still exists, to restore it.

Reading this with an AI assistant? Plain Markdown version.