> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/guides/guides/campaigns/campaign-automations.md).

# Campaign automations

Rules inside a campaign that run an action when a contact interacts with its components: how they work, which ones are available, and how they differ from Journeys.

Campaign automations are rules inside a campaign. Each rule runs one action, such as sending an email or adding the contact to a list, when a contact does something with one of the campaign's components.

Use them for simple, immediate follow-ups to a send or a form, for example a confirmation email when a form is submitted, or a notification to a colleague when a link is clicked. They are quick to set up, they live with the campaign, and they are copied along when you copy the campaign.

## Find a campaign's automations

Open the campaign and click the **Automation** tab. The **Automation rules** list shows each automation with its trigger (**When this happens**), its action (**Do this**), any delay, whether it runs only once per contact (**Limitation**), and how many contacts it has run for.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-ed9dd02bb2e1b0bb9e37d778831338328732a370%2Fcampaign-automations-automation-tab.png?alt=media" alt="The Automation tab of a campaign with the Automation rules list and the New automation button"></div>

## Create an automation

1. Open the campaign and click the **Automation** tab.
2. Click **New automation**.
3. Choose the action that should happen.
4. Fill in the settings for the action. Each automation's settings are described in its own article below.
5. Under **When this happens**, choose the trigger. See [Choose the trigger](#choose-the-trigger).

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-aba363d55ad3665dcfc8f14dc88ad1fdf8b6339f%2Fcampaign-automations-new-automation-panel.png?alt=media" alt="New automation panel listing the available automations, from Send email to Send notification"></div>

## Choose the trigger

Every automation has a **When this happens** section at the bottom. It sets which event in the campaign runs the automation.

1. **Select Component** — choose one of the campaign's components. Only components in the same campaign can trigger its automations.
2. **Select Event** — choose what the contact must do with that component.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-70465f754194a4b89a8868fcfec41d23fb8351b8%2Fcampaign-automations-trigger.png?alt=media" alt="Send email automation settings with the When this happens section, where you select the component and the event"></div>

The events depend on the type of component:

* **Email** — **Is opened**, **Is sent**, **Any link is clicked** or **A specific link is clicked**.
* **Form** — **Is submitted**.
* **Form (Legacy)** — **Is submitted** or **Specific answer**, which triggers when a specific option in a multiple-choice question is answered.

{% hint style="info" %}
Email opens are an unreliable trigger. Some email clients block images, and an open is only registered when images load. Use a click as the trigger when you can. See [When is an email registered as opened?](https://support.emarketeer.com/references/references/email/email-open.md).
{% endhint %}

## Settings all automations share

* **Name** — a name for the automation, shown in the **Automation rules** list.
* **Do only once per contact** — selected by default. The automation then runs at most once for each contact, even if the contact triggers the event again.
* **Delay action** — available for the **Send email** and **Send SMS** automations. Waits the set time after the trigger before the message is sent.

## Copy or transfer a campaign

When you copy a campaign, its automations are copied with it, so the copy works the same way. When you [transfer a campaign to a different account](https://support.emarketeer.com/guides/guides/campaigns/transfer-a-campaign-to-a-different-account.md), the automations are not transferred.

## Available automations

* [**Send email automation**](https://support.emarketeer.com/guides/guides/campaigns/campaign-automations/campaign-automation-send-email.md) — send an email message to the contact.
* [**Send SMS automation**](https://support.emarketeer.com/guides/guides/campaigns/campaign-automations/campaign-automation-send-sms.md) — send an SMS message to the contact.
* [**Add to list automation**](https://support.emarketeer.com/guides/guides/campaigns/campaign-automations/campaign-automation-add-to-list.md) — add the contact to a contact list.
* [**Remove from list automation**](https://support.emarketeer.com/guides/guides/campaigns/campaign-automations/campaign-automation-remove-from-list.md) — remove the contact from a contact list.
* [**Add to campaign automation**](https://support.emarketeer.com/guides/guides/campaigns/campaign-automations/campaign-automation-add-to-campaign.md) — add the contact to another campaign.
* [**Remove from Campaign automation**](https://support.emarketeer.com/guides/guides/campaigns/campaign-automations/campaign-automation-remove-from-campaign.md) — remove the contact from a campaign.
* [**Update contact card automation**](https://support.emarketeer.com/guides/guides/campaigns/campaign-automations/campaign-automation-update-contact-card.md) — update fields on the contact record.
* [**Update legal basis automation**](https://support.emarketeer.com/guides/guides/campaigns/campaign-automations/campaign-automation-update-legal-basis.md) — set the legal basis for storing and marketing.
* [**Update subscription automation**](https://support.emarketeer.com/guides/guides/campaigns/campaign-automations/campaign-automation-update-subscription.md) — subscribe or unsubscribe the contact.
* [**Withdraw consent automation**](https://support.emarketeer.com/guides/guides/campaigns/campaign-automations/campaign-automation-withdraw-consent.md) — withdraw the contact's consent for marketing sendouts.
* [**Send notification automation**](https://support.emarketeer.com/guides/guides/campaigns/campaign-automations/campaign-automation-send-notification.md) — send a notification by email or SMS.

If you have connected SuperOffice, see also [SuperOffice automations](https://support.emarketeer.com/integrations/superoffice/superoffice-automations-pro.md).

## Campaign automations and Journeys

Campaign automations and [Journeys](https://support.emarketeer.com/guides/journeys.md) can perform many of the same actions. Choose the one that fits the task:

* Use a **campaign automation** when one action should happen right after an event in this campaign, such as a form submission or a link click.
* Use a **Journey** when you need several steps, waits, If / Else branches or conditions, or a trigger outside the campaign. See [Journey Steps](https://support.emarketeer.com/guides/journeys/journey-steps.md).

Many automations have a Journey step that does the same thing:

| Campaign automation  | Closest Journey step                                                                                                    |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| Send email           | [Send Email](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-send-email.md)                   |
| Send SMS             | [Send SMS / Text message](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-send-sms.md)        |
| Add to list          | [Contact List](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-contact-list.md)               |
| Remove from list     | [Contact List](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-contact-list.md)               |
| Add to campaign      | —                                                                                                                       |
| Remove from Campaign | —                                                                                                                       |
| Update contact card  | [Update Contact Card](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-update-contact-card.md) |
| Update legal basis   | [Legal Basis](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-legal-basis.md)                 |
| Update subscription  | [Update Subscription](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-update-subscription.md) |
| Withdraw consent     | —                                                                                                                       |
| Send notification    | [Notify stakeholder](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-notify-stakeholder.md)   |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.emarketeer.com/guides/guides/campaigns/campaign-automations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
