> ## Documentation Index
> Fetch the complete documentation index at: https://loops.so/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Workflows
> Workflows let you send emails based on something happening, like a contact property updating, a new contact being created or an external event happening in another platform.
Our automation feature "Loops" has been renamed to "Workflows".
## Getting Started
To start building your workflow, select a template or start from scratch.
Templates are added often and we're always open to taking suggestions!
## Building a workflow
A workflow is an email sequence that can be triggered by different events and contain emails, delay timers and branches.
You can add new nodes to your workflow by hovering over an arrow between nodes and clicking the `+` button.
More complex workflows can be built by [adding branches](/workflows/branching).
## Zoom and canvas navigation
You can zoom in and pan around the workflow canvas, which makes it easier to work with larger and multi-branch workflows.
Zoom and panning uses typical trackpad and mouse gestures, so should be familiar.
**On a trackpad**
* Pinch to zoom in and out
* Use two fingers to pan around the canvas
**With a scroll-wheel mouse**
* Use `⌘/Ctrl` and the scroll wheel to zoom
* Use the scroll wheel to pan vertically
* Use `Shift` and the scroll wheel to pan horizontally
To reset your view back to 100%, click the "Zoom" button that appears at the bottom of the canvas.
## Mailing lists
You can make a workflow send to a specific mailing list by using the dropdown in the top right of the workflow builder.
By selecting lists from this dropdown you can make sure that only contacts from those lists are added to the workflow.
When using the **Contact added to list** trigger, this option is removed and
you can instead select the list from the trigger node.
## Nodes
There are six types of nodes available in workflows:
* Trigger
* Email
* Timer
* Audience filter
* Branch ([read more](/workflows/branching))
* Experiment ([read more](/workflows/experiments))
### Triggers
The first node to add to a workflow is the trigger. This is what will send new people into the workflow.
There are four trigger options:
* **Contact added**: Triggered whenever a contact has been added to your audience.
Only contacts who have been added via a [form](/forms/simple-form), the
[API](/api-reference/intro) or an [integration](/integrations) will be added
based on this trigger. Contacts added individually to the audience table
will not be included. Contacts added or updated via CSV will only trigger if
you select the [Trigger workflows](/add-users/csv-upload#trigger-workflows-via-csv)
toggle during upload.
* **Contact updated:** Triggered whenever a contact property changes from one value to another. Can also conditionally trigger only if the previous property matches the inputted value.
* **Contact added to list:** Triggered whenever a contact is added to a certain [mailing list](/contacts/mailing-lists). You can select the list from the trigger node.
* **Event received**: Triggered when a certain [event](/events) is sent to Loops by the API or an integration. With this trigger you can start a workflow based on interactions in your app. Common custom events are `signUp`, `canceled` and `activated`.
You can read more about triggers [here](/workflows/triggers).
### Emails
You can add emails at any location inside your workflow, giving you flexibility to send mail immediately after the trigger or after a delay. You can also send to specific contacts by adding an audience filter, or by branching your workflows.
You can add unlimited emails to each workflow.
To edit an email, click on the email node, then **Edit email**.
When a workflow is active, you cannot edit the email. Click **Pause** to pause the workflow and make changes to your email (and any other nodes). While paused, new contacts will be queued for up to 24 hours; they will enter your workflow as soon as you save your email by clicking **Resume**.
You can copy emails from other workflows by clicking the **Copy existing email** button after creating a new email node. This will bring up a dropdown of emails from other workflows that you can insert into your workflow.
### Timers
A timer adds a fixed time period between two nodes in the workflow.
For example, you could add a "3 day" timer after a "Contact added" trigger to send an email three days after a signup.
You can select the “Immediately” option to bypass the timer or any increment of time to extend the duration of the workflow.
You can add multiple timers to your workflows, to add delays in different parts of your workflow.
### Audience filters
Audience filters let you create fine-tuned workflows to target specific contacts.
For example, you can check in with contacts that have not signed up as a paying user 3 days after signing up by setting the Custom Event to `signup` the Timer duration to 3 days and the audience filter to `paid` equals `false`.
There are two options for applying audience filters:
* **All following nodes**: this will apply the filter when contacts reach every following node. If a contact no longer matches the filter's audience when they reach a following node, they will be removed from the workflow.
* **Next node only**: this will apply your filter before contacts reach the next node. This is a one-time filter and any changes to the contact's value after the filter will not be taken into account.
Learn how to branch workflows using audience filters.
## Metrics
Click over to the **Metrics** tab to view simple metrics inline within the builder.
Click **View details** to view detailed metrics for your workflow.
## Testing workflows
You can test if a workflow works as expected by using email addresses with `@example.com` and `@test.com` domains (for example `test@example.com`).
First, add these as contacts in your audience, then depending on how your workflows are set up, you can add and update properties, or send events to these email addresses to see how contacts move through your workflows.
Emails will not be sent to `@example.com` or `@test.com` email addresses so this is a good method to test emailing contacts without affecting your sending domain’s reputation.
You can also send test emails for each of the emails in a workflow. Click on an email node and then the **Send a preview** airplane icon above the preview that appears.