Test, go Live, pause

Test each step

In the course

• VCEach step is tested with a sample enquiry before the first real parent sees it. Lesson 1: Reply to every enquiry in seconds →

Testing runs one step for real, using the sample data from the steps before it. It’s the best way to catch a wrong field before customers do.

1. Make sure the steps before it have data: capture a sample on the trigger, and test earlier steps first.
2. Open the step, go to the Test tab, and click Test This Node.
3. Read the output. For a trigger, Sample Data Preview shows the captured fields.

A successful test saves the output as this step’s sample (so later steps can map it) and switches the step to Live. If the test fails, the panel shows the app’s error; see Troubleshooting.

Tests are real

A test of Send a message really sends a message, and a test of Insert a row really adds a row. Tests also count as tasks. Test with your own phone number and a test sheet first.

autoappy.com/workflows/…Sample data

A trigger's Test tab after capturing a sample.

×

Change the status

Open ⋯ (More) at the top right and choose a Workflow status:

Status	Meaning
Draft	Not running while you build.
Live	Runs when its trigger fires or on schedule.
Paused	Keeps everything, runs nothing.

autoappy.com/workflows/…Sample data

⋯ → Workflow status.

×

You can also change status from the Agents list: open the row’s ⋯ menu, then Status.

What has to be Live

• The workflow must be Live.
• Its trigger must be Live. Capturing a webhook sample switches both on for you.
• Each step must be Live to run. Testing it switches it on. Draft or Paused steps are skipped.

Pausing

Paused keeps the workflow, its steps, connections and history exactly as they are. A paused webhook workflow answers callers with “The workflow or trigger is paused or in draft.” (HTTP 409), so nothing is lost silently: the sender sees it was refused.

Run once

Run once (top right) starts the workflow straight away. It’s only available when the workflow starts with an action rather than a trigger, for example a workflow that begins with Get Row(s) from Sheet. For trigger-based workflows, the button explains: “Trigger workflows run when their trigger receives an event.” To test those, send a real event (submit the form) or test steps one by one.

A pre-flight checklist

• Every tile is free of plug and pencil badges.
• The status bar shows nothing to review.
• The workflow and trigger say Live.
• You’ve sent one real event and checked it in History.
• Messages go to the right people (test with your own number first).

Run history

Troubleshooting