> For the complete documentation index, see [llms.txt](https://docs.acymailing.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acymailing.com/main-pages/scenario/create-a-new-scenario.md). # Create a new Scenario ### Triggers To create a new scenario we will have to go to the Scenario menu and click on Create button:

Then you can start by selecting a trigger:

Triggers are always specific to one user, here are examples of triggers: * Subscriber creation: When a subscriber is created * Subscribers subscribe: When a subscriber subscribes to a list * Subscriber opens an email: When a subscriber opens a specific or any email * On subscriber's birthday: When it's the birthday of the subscriber ### Scenario Editor Once you've chosen a trigger, you can start editing your scenario. For example, let's say you want to send an email with a subscribe link to a subscriber who opened a specific email, then check if they subscribed to send them another email. First, we set a delay of 1 hour, this way the email is not sent right away:

Then we can add an action to send an email:

Clicking the Create new email button will redirect you to the email creation page, in which we include a dynamic text:

Once the action is added we need to add a new delay to let the subscriber have time to open it and click on it.

We can then add a condition to check if the subscriber has subscribe to the list Newsletter:

Now you can add another action to send another email to subscribers who only subscribe to the list Newsletter:

Once you've finished creating your scenario you'll have to save it:

In this case, you can activate the **Trigger once** option to make sure this scenario is triggered only once time on the subscriber, if this option is not activated the scenario will be triggered every time. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.acymailing.com/main-pages/scenario/create-a-new-scenario.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.