​

Automation Debugger

Courier’s automation debugging tool can be used to run a test event through your automation template and debug any errors you may come across.

​

Creating a Test Run Context

Similar to notification templates, automations can now be tested with test run contexts passed in and saved as test events. These tests can mimic an incoming payload passed through Segment, inbound events, or an adhoc automation call. You can create a test event from the Debug tab in your automation template.

​

Running The Test Run Context

With your automation test event configured, you can execute a test run through the debugging tool to simulate the event passed through the automation workflow. When ready, click on the Run Again button and select each node to see the data being passed.

​

Verifying Test Data

After running your simulated run, you can select each node in your workflow to verify that the data is passed through to each consecutive node. This can be helpful if you have several nodes that rely on incoming data payloads.

​

Run your Automation

After testing through the debugging tool, you can run your automation through an API call with the data payload you wish to pass.

// POST https://api.courier.com/automations/:template_id/invoke
{
	"data": {
    "field_1": "fubar",
    "field_2": "fubar2"
},
  "profile": {
    "email": "rodrigo@courier.com",
    "phone_number": "+12345678910",
    "name": "Rod"
}
}

The automation run context will be show a successful run through the automation workflow with the data we tested!

​

Testing GET Profile Nodes

You can leverage Courier’s debugging tool to test out a GET Profile node before promoting your template to production. The debugging tool can show you the run context that will be passed down your automation after fetching a profile.