Test an Integration Action Before You Publish

Steps that call an external app have a Test Action button. It runs that one step for real, using your connected account and the values you filled in, and shows what was sent and what came back. That means you can verify a setup without publishing and enrolling a test contact.

Before you test

• The app must be connected on the action's account dropdown.
• Every required field needs a value, either typed in or mapped from the workflow. The button stays disabled until they are complete.
• If the step uses data from an earlier step, that earlier step needs a saved sample or must have been tested first.
• The test is a live request, so it can fail if the outside service is down or limiting requests.

Run a test

1. Open the workflow and click the integration action you want to check.
2. Fill in all required fields.
3. Click Test Action.
4. A drawer opens with two panes: Data In (what was sent) and Data Out (the response, with key values summarized above the raw data).
5. If it worked, click Use this as sample to save the response shape.

Why saving a sample matters

Once saved, every field in the response, including nested items, becomes selectable in later steps and conditions. You can map a returned ID into the next action without guessing its name.

Be careful with live data

A test performs the real operation. Testing a Create or Delete step will actually create or remove a record, so use a test record when possible.

Good to know: If a test fails, read the error code in the Data Out pane first; it usually names the field or permission at fault.