> For the complete documentation index, see [llms.txt](https://docs.funnelish.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.funnelish.com/automations/actions/conditions.md).

# Conditions

Use conditions to split an automation and perform different actions depending on customer behavior. 

{% embed url="<https://youtu.be/HW4phrwD0os>" %}

Here is an example. Let's say you want to send people an order confirmation email, but you want to send two types of messages: one for people who bought the main product plus the upsell and one for people who bought the main product but not the upsell. Adding a condition to the automation lets you generate two conditional actions and automatically send two different kinds of messages.&#x20;

## 1  Open an automation

Open an automation and click the plus (+) button.

<div align="center"><figure><img src="/files/9WKMaqPpgSSkAeVuK8WZ" alt=""><figcaption></figcaption></figure></div>

&#x20;Select **Workflow** and click **Condition.**

![](/files/-MW5VlU1HsimLVQs2zpy)

## 2  Add conditions

Create a condition on the first row. In the example below, we are looking specifically for customers who purchased an item from the Upsell page. <br>

<figure><img src="/files/TmCVN1UNfrD1dSLKhYrA" alt=""><figcaption></figcaption></figure>

**Add another condition** (optional).&#x20;

If you want to narrow down the condition, click **(+) Add another condition** or **(+)Add new block** to add more rules.

Depending on your needs, select AND (all rules must apply for the condition to be true) or select OR (any rule must apply for the condition to be true).&#x20;

<figure><img src="/files/TbB5hmo6et4MHHOJRvVP" alt=""><figcaption></figcaption></figure>

Click **Add** when you're done.&#x20;

Funnelish displays the split in your automation.

![](/files/6ZE5tz5a4UCnszor6KyU)

&#x20;From here, you can build your automation further based on whether the customer does or does not pass the conditions!


---

# 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.funnelish.com/automations/actions/conditions.md?ask=<question>&goal=<endgoal>
```

`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.