> For the complete documentation index, see [llms.txt](https://docs.ubiquity.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ubiquity.co.nz/documentation/how-to/activate.md).

# Activate

Set up and manage automated or triggered communications based on customer behaviour.

Before an automated send or triggered communication will run, it needs to be activated. Activation is the final step in the setup wizard across several areas of UbiQuity.

Once activated, the dashboard updates to show reporting and a history of runs. The send will continue to run on its configured schedule or trigger until you deactivate it.

To make changes after activation, deactivate first, edit, then reactivate.

***

### Activating your send

Activate is the often the final step in the setup wizard. Before activating, review your settings - once active, some fields are locked until you deactivate.

Use **Run Now** where available to trigger the send immediately outside of its regular schedule.

The Activate option appears when you hit Finish on the final step of the wizard, as well as on the Dashboard screens. While the exact placement varies by area, the button looks the same throughout UbiQuity.

<figure><img src="https://29319303-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFTPPHEKVW9ESLfGpxTpi%2Fuploads%2Fg78b9PRc8zMgWzVBGsQn%2FScreenshot%202026-04-28%20at%2010.15.29%E2%80%AFAM.png?alt=media&amp;token=bf7ab78d-3665-452c-846c-5a0bacac2ee1" alt=""><figcaption><p>Here is an example of an Activate button appearing on the Automated Mailout Dashboard screen.</p></figcaption></figure>

<div align="left"><figure><img src="https://29319303-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFTPPHEKVW9ESLfGpxTpi%2Fuploads%2FW1Qb4Yjkkw9hkUE7JTJh%2Fimage.png?alt=media&amp;token=1f33e6c4-6c93-4ecf-9f16-7c4caf55d35e" alt=""><figcaption></figcaption></figure></div>

***

### Where Activate applies

* Automated Mailouts
* Automated TXT Outs
* Automated Notifications
* Forms and triggered emails
* Surveys and triggered emails
* Events and triggered emails


---

# 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://docs.ubiquity.co.nz/documentation/how-to/activate.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.
