Deploy, test and change a workflow

Deploy a workflow before its first run, test with safe data, review live changes carefully, and pause the workflow when you need to.

At the end of this page you will have deployed a workflow, run it once, and know how to change it, pause it or go back to an earlier version safely.

Before you start

Every step that uses a system needs its account chosen. Deploy checks the steps and stops if one is incomplete.
Plan your first runs with test data, such as a test customer or a sandbox company. A run does real work in your connected systems.

Deploy and run it

Press Deploy

In the editor's top bar, press Deploy. The Deploy Workflow window shows the Current Version. If it warns about unsaved changes, close it, wait for the save, and press Deploy again.

Confirm

Press Deploy in the window. You see "Workflow deployed", and the status changes to Active. The trigger now starts the workflow.

Run it once

Press Run. In the Run Workflow window, leave Input (JSON) as it is unless your developer gave you values to enter. Press Run.

Read the result

Press View Runs and open the run. Check what each step received and produced. See Read a run step by step.

Run works only on an Active workflow, so deploy first even when you only want to test. Pressing Run on a Draft or Paused workflow shows "Workflow must be active to run".

Change a live workflow

Edits to an Active workflow are saved as you work, and its next run uses them. There is no separate test copy. So for anything more than a small fix:

Make the change on a copy. On My workflows, open the workflow card's menu and choose Duplicate. The copy starts as a Draft with the same trigger. Before you deploy it to test, swap its trigger to API so only Run starts it. Then change and test the copy, and make the same change on the original.
Or pause while you edit. Pause the workflow so its trigger stops starting it, make the change, then Deploy again. A paused workflow cannot be run, so test with a copy before you deploy a large change.

After you change an active workflow, Deploy becomes available again. Press it to record the change as a new version in Version History.

The clock icon in the top bar opens Version History. It lists past versions with the date of each. Press Rollback next to a version, then Confirm, to restore it. The restored steps become the newest version, and the workflow keeps its status.

Take a workflow offline

You want to	Do this	What happens
Stop it for now	Version History > Pause	Status becomes Paused. Its trigger stops starting it. Press Deploy to switch it back on.
Put it away	Gear icon > Archive	It moves to the Archived tab and stops running. Its schedule and inbound email address are removed.
Bring back an archived workflow	Gear icon > Unarchive	It returns as a Draft. Deploy it again to switch it on.
Remove it for good	Archive it, then gear icon > Delete	You type the workflow's name to confirm.

Check it worked

The status next to the workflow's name reads Active.
Your test run is listed under Runs.

If something goes wrong

Deploy is greyed out. There is nothing new to deploy, or the workflow is archived.
Deploy fails. A step is incomplete or its trigger is missing a setting. Read the message in the window, fix the step, and deploy again.
Run shows "Workflow must be active to run". Press Deploy first.
The run failed. See Fix and retry a failed run.