Test action feature for integrations

Overview

You can now run live tests on every external-app action step inside the EveryCatch Workflow Builder. Before you turn a workflow on, you can validate your inputs, send a real call to the connected app, see the exact payload that went out, review the raw response that came back, and let EveryCatch automatically detect the response structure so those fields are ready to use in later steps.

The Test Action feature helps you verify an integration step while you are configuring it, instead of waiting to see what happens only when the workflow runs.

What changed

• Every external-app action step in the Workflow Builder now includes a Test Action button.
• From the action configuration card, you can click Test Action to open the testing view and walk through a full live test of that step. The button appears on all supported external-app actions.

Live test execution

• When you test, the action calls the connected app using a real API request, with the actual input values resolved from your current builder setup.
• Workflow variables, custom values, and any transformations you have configured are applied in the test exactly the same way they will be when the workflow runs.
• The test uses the same connected account the action will rely on during normal workflow execution, so you are seeing a true end-to-end run.
• You get side-by-side Data In and Data Out panes to understand what happened in detail.
• Data In shows the final values that EveryCatch is sending to the provider, after variables are filled and transformations are applied.
• Data Out shows the raw JSON response from the provider. You can scroll through large responses, and key fields appear as inline chips and cards above the expandable JSON to make them easier to spot and reuse.

How it works

• Set up the action as you normally would: choose the integration, select the action type (for example, Find Contact in Klaviyo), and map all required input fields.
• If the action relies on custom values coming from earlier workflow steps, EveryCatch needs to be able to resolve those values before you can run a test. The Test Action button only becomes active when all referenced custom values are available for the test.
• Click Test Action. A Test Drawer opens from the right side of the screen and shows a progress state while the request runs.
• EveryCatch sends the live request. If it succeeds, the Test Drawer fills with the Data In and Data Out views, and key fields from the response appear as chips and cards above the expandable JSON.
• Review the response details so you can confirm the action is working as expected and adjust your mapping or downstream steps if needed.