The Automations Designer

​

Creating an Automation

Start by navigating to the automations page within the Courier app. From there, a new automation template can be created by clicking the New Automation Button.

​

Renaming an Automation

To rename a template, click the name in the upper left hand corner of the designer. By default, the name is “Untitled Automation”. The name is automatically saved after being updated.

​

Working with Automation Nodes

A new template starts with two placeholder nodes. A trigger placeholder, and an action placeholder.

The top placeholder with acts as a placeholder for an automation trigger node. A trigger node defines what starts an automation run. The trigger is optional, a template can always be directly triggered using the api/automations/:template_id/invoke api endpoint

The bottom one acts as a placeholder for action and control flow nodes.

To add nodes, expand from the list on the left and then click and drag a node onto the right. The first trigger and action node will snap into their respective placeholders:

​

Automation Invocation

There are a few ways to invoke a template, either directly in the automation template, through a trigger node, or through an api call.

See Scheduling automations or Triggering With Segment to get an understanding of how trigger nodes work.

​

Invoking an Automation using the API

To run an automation by api call, grab the automation template id or the alias from the settings section of the designer and invoke it by calling POST api/automations/:template_id_here/invoke. View Automations API docs for more details.

​

Invoking an Automation from the Designer

You can invoke the automation template directly from the designer in the Invoke tab. This can be a good way to test the automation or to invoke very simple automation templates. Note: Invoking from the designer will pass an empty data payload {} to the automation run