When the trigger fires, the workflow runs and its action posts JSON to a web address you choose. Triggers cover an order placed, paid, refunded or canceled, a ticket issued, voided or checked in, and an attendee's details changing.

Start one from New workflow, then fill in its When slot, its Only if… line and its Then slot.

Reading the list

A line under each workflow's name describes it: the trigger, the condition where it has one, and where each outcome goes. A workflow still missing an action, or an action still missing its address, says not finished there.

The Last 7 days column counts the runs that went out and the ones that came back failed. "Nothing in 7 days" means it has run before and not lately, which is worth a look: a workflow whose trigger stopped happening stops running without ever failing.

When a switched-on workflow's most recent run failed, the list says so at the top of the page, names the workflow and links straight to that run. The notice clears once the workflow runs successfully again, or as soon as you switch it off.

Checking what will go out

The Then step shows What gets sent under its field table: the JSON body one run would produce, using a recent order or ticket from this account as the example. A step that has to send a particular shape shows that shape with your values in it, rather than a plain list of the fields. A step with no fields at all still has a body, and the block shows the one it sends every time.

Fields that come out empty are listed under Empty fields. A key that no field in this account has is marked as a problem, and that row is empty on every run until you correct the key. A key that's real and unanswered by this example says so, and a run with a real answer sends it.

A step that has to send a particular shape names the fields it wants inside that shape. A name that isn't in the field table is marked as a problem in that same list. No example will ever fill it in, so it goes out empty every time until the names match.

Removing a field

Every field you have saved has a bin icon at the end of its row in the Fields table. It opens a page naming the field and the address it was going to, and Remove field there takes it out. The rest of the fields keep going out as before.

A row you are still filling in has no icon, because nothing is being sent under that name yet. Neither do the fields that come with a step like Brella, which sends a shape that service expects and needs every name in it.

Good to know

Which events this covers scopes where a workflow fires. Every event includes events you create later. Only the events I pick opens your event list right there, and unticking an event stops the workflow running for it.
A run that fails because the other service was down, overloaded or slow to answer tries again on its own, after a minute, then five, then half an hour, then two hours, and gives up after that. While it's waiting it appears under Activity as still to run.
Deleting a workflow deletes its run history and event subscriptions with it.
A run's own page holds still while the run is working, so Run again stays where you left it. Press Check now to see where the run has got to.
To run one workflow for one person or one order, open that attendee or order and pick the workflow by name under Actions. The confirm step names where it sends before anything goes out.
The Workflows line on an attendee or an order names each workflow that covers it and what it last did. The name opens the workflow, and the line opens everything that has happened to that record.

The switch waits until the workflow could do something.

Enabled stays out of reach while anything is missing, and says which thing beside it: "Add a web address before you can turn this on". Disabling always works.