# Create an Automation

Use the Automation composer to automatically send a message to users when predefined conditions are met.

> **Note:** Each automation counts toward your *Sequences and Automation* [Message Limit](https://www.airship.com/docs/reference/glossary/#message_limits).


To get started, access the Automation composer:

1. Select **Create** in the sidebar.
1. Next to **Build from scratch**, select **View all**.
1. Select **Automation**.

Next, enter a message name and save it. After completing a step, select the next one in the header to move on.

## Setup


First, [configure the trigger](https://www.airship.com/docs/guides/messaging/messages/sequences/triggers/) that will initiate your automation, and enable the channels you want to send the message to.

Then, configure options: [Cancellation Events](#cancellation-events), [Conditions](#conditions), and [Rule Limits](#rule-limits). Last, set up [Channel coordination](#channel-coordination).

### Cancellation Events

*Cancellation events* are Custom Events that prevent an Automation, Sequence, In-App Automation, or Scene from sending/displaying if they occur while the Automation (or other) is in a delay period. Not supported for the Inactivity trigger.

To configure, complete the same workflow used for the [Custom Event trigger](https://www.airship.com/docs/guides/messaging/messages/sequences/triggers/#custom-event). This includes the option to [filter](https://www.airship.com/docs/guides/messaging/messages/sequences/triggers/#filtering-custom-events) the cancellation events.

> **Important:** Cancellation events require a delay of at least one hour to ensure that there is time for the cancellation event to occur after the original triggering event occurs. In the *Delivery* step in an automation, you must specify a delay of at least one hour.


### Conditions

Conditions are requirements your audience must meet in order to receive a message from an automation. You can base conditions on whether a user has or does not have a specific [Tag](https://www.airship.com/docs/reference/glossary/#tag), which includes [Predicted to Churn status](https://www.airship.com/docs/reference/glossary/#predicted_to_churn) and [Device Property](https://www.airship.com/docs/reference/glossary/#device_properties) tags, or whether or not they are a member of a [Subscription List](https://www.airship.com/docs/reference/glossary/#subscription_list).

> **Tip:** If sending an SMS message, you can use conditions to restrict your message audience to a particular [Sender ID](https://www.airship.com/docs/reference/glossary/#sender_id). Either search for a sender ID, or select the Sender ID filter before searching.


To configure:

1. Select **Add a condition**.

1. Search for the data you want to use as a condition. To filter results, select the filter menu () and make your selection. Search behavior varies by filter:
   * **All (no filter selected):** Search within all condition types.
   * **Tags:** Search for [primary device tags](https://www.airship.com/docs/guides/audience/tags/#device-tags) (tags in the `device` tag group).
   * **Tag Groups:** Search for and select a tag group, then search within that tag group.
   * **Predicted to Churn:** Search for all or part of `High`, `Medium`, `Low` or `Predicted` only.
   * **Subscription List:** Search subscription list names only.

   To create a new tag using your search term, click **Create [search term]**.
1. Select the logic for the condition:
   * **Has** means the user must have the tag or be a member of (opted in to) the subscription  list to receive the message.
   * **Doesn’t Have** means the user must not have the tag or be a member of (not opted in to) the subscription list to receive the message.

1. After adding all conditions, use the **Any**/**All** Boolean selector to determine which conditions must be satisfied before the message will be sent.

### Rule Limits

*Rule limits* cap the number of messages a user can receive from an Automation within a time frame, preventing you from over-messaging your audience, e.g., a maximum of 1 per day. Rule limits are set per Automation.

To configure, select **Add a Daily Limit** and/or **Add an All-Time Limit** and enter a number.

### Channel coordination

<p>First, select a [Channel Coordination](https://www.airship.com/docs/reference/glossary/#channel_coordination) strategy:</p>
<ul>
<li><strong>Fan Out</strong> targets a Named User on all the channels they are opted in to, maximizing the chances they receive your message.</li>
<li><strong>Last Active</strong> targets a Named User on the opted-in channel they used most recently.</li>
<li><strong>Priority Channel</strong> targets a Named User on the first channel they are opted in to, in the priority order you set.</li>
</ul>
<p>Then, enable the channel types to include in your audience. For Mobile Apps, also select from the available platforms. For Priority Channel, also drag the channel types into priority order.</p>

> **Note:** For projects using the [channel-level segmentation system](https://www.airship.com/docs/guides/audience/segmentation/segmentation/#channel-level-segmentation), instead of channel coordination, enable the channels you want to send the message to. Available channels are based on your trigger.
> 
> ![Enabling channels for an Automation](https://www.airship.com/docs/images/automation-setup_hu_c55295eb0c3c25c9.webp)
> 
> *Enabling channels for an Automation*


## Content

Configure the message content per enabled channel. See [Content by channel](https://www.airship.com/docs/guides/messaging/messages/content/).

![Configuring message content per channel in the composer](https://www.airship.com/docs/images/composer-content-app_hu_28a88387be2dfd33.webp)

*Configuring message content per channel in the composer*

## Delivery

Configure [delivery](https://www.airship.com/docs/guides/messaging/messages/delivery/delivery/). Timing settings do not appear if you chose the Inactivity trigger.

<!-- Do we want an image here? -->

## Review {#message-review}

Review the device preview and message summary. Click the arrows to page through the various previews. The channel and display type dynamically update in the dropdown menu above. You can also select a preview directly from the dropdown menu. If you want to make changes, click the associated step in the header, make your changes, then return to *Review*.

Send a test message to verify its appearance and behavior on each configured channel. The message is sent to your selected recipients immediately, and it appears as a test in [Messages Overview](https://www.airship.com/docs/reference/glossary/#messages_overview).

1. Select **Send Test**. <ol>
<li>
<p>Under <strong>Test audience</strong>, enter at least one [Named User](https://www.airship.com/docs/reference/glossary/#named_user) or [Test Group](https://www.airship.com/docs/reference/glossary/#preview_test_groups) and select from the results. If your message includes email, you can also search for email addresses. If no matches appear for an address, you can select <strong>Create channel for &lt;address&gt;</strong>, and the channel will be registered for your project and opted in to transactional messaging.</p>
<p>Users in an active [Holdout Experiment](https://www.airship.com/docs/reference/glossary/#holdout_experiment) will not receive a test message. You can view a user&rsquo;s current holdout group status and history when <a href="https://www.airship.com/docs/guides/audience/contact-management/#viewing-channel-details">viewing their channel details in Contact Management</a>.</p>
</li>
<li>
<p>(If your message contains [Handlebars](https://www.airship.com/docs/reference/glossary/#handlebars)) Under <strong>Personalization</strong>, select and configure a personalization data source:</p>
<table>
  <thead>
      <tr>
          <th>Data source</th>
          <th>Description</th>
          <th>Steps</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td><strong>Test message recipient</strong></td>
          <td>The message will be personalized using information associated with each test audience member.</td>
          <td>n/a</td>
      </tr>
      <tr>
          <td><strong>Preview Data tool</strong></td>
          <td>The message will be personalized using the data currently entered in the <a href="https://www.airship.com/docs/guides/personalization/previewing/">Preview Data tool</a>. The same values will apply to all test message recipients. You can also manually edit the JSON.</td>
          <td>(Optional) Edit the JSON data.</td>
      </tr>
  </tbody>
</table>
</li>
<li>
<p>Select <strong>Send</strong>.</p>
</li>
</ol>

Choose whether to create this automation as *Active* or *Paused*. Select Paused if you’d like to create the message but aren't quite ready to activate it. After starting your automation, you can [change its status at any time](https://www.airship.com/docs/guides/messaging/manage/change-status/).

When ready, select **Start Automation** or **Schedule Automation**.

## Convert an Automation to a Sequence

Convert an Automation to a Sequence so you can use features like [Control Groups](https://www.airship.com/docs/guides/experimentation/control-groups/), [Test Run](https://www.airship.com/docs/guides/messaging/messages/sequences/create/test/), and [A/B Testing](https://www.airship.com/docs/guides/experimentation/a-b-tests/sequences/). You can also add more messages.

After conversion:

* The Automation name is copied to the Sequence.
* The Automation trigger and settings are copied to the Sequence.
* The Automation message content and settings are copied to the first message in the Sequence.
* The Sequence status is the same as the Automation status at the time of conversion: *Started* if the Automation was active, and *Paused* if the Automation was paused, or *Draft*.
* The converted Automation is archived and cannot be un-archived.

To convert to a Sequence:

1. Go to **Messages**, then **Messages Overview**.
1. Click the duplicate icon (
) for an Automation, and select **Convert to: Sequence**.

The next screen will be the [Sequence Manager](https://www.airship.com/docs/reference/glossary/#sequence_manager) for the new Sequence.