# Automations

Reo.Dev Automations help you act instantly on intent by pushing real-time account, developer, and buyer signals directly into your Slack or other tools (using webhooks).

Whether it’s a surge in activity, a new developer or buyer being identified, a new account showing activity —you get the updates where you need them, without any manual effort. 

**Automations has 4 components:**

1. **Source**

The object you want to run the automation on — a **segment** (account, developer, buyer) or a **list** (account or developer)

**2. Trigger**

The event that fires the automation. Each source comes with a predefined set of available trigger for every segment and list type.

**3. Condition (Optional)**

Additional filters or criteria that must be met for the automation to run.

**4. Action**

Where the data goes — Slack (channel or DM) or Webhook via Zapier.

{% hint style="info" %}
**Pre-requisites:** 

To use **Automations** in Reo, you’ll need at least one of the following set up:

1. **Slack Integration**: To get alerts on slack - please ensure that your slack workspace is integrated to Reo. [Here's a quick guide on how to set it up.](https://docs.reo.dev/settings/configure-slack-and-email-notifications)
2. **Configure Webhooks**: To trigger workflows in other tools, please configure webhooks. [Here's the complete guide on creating webhooks. ](https://docs.reo.dev/integrations/webhooks)

{% endhint %}

### **Create an automation:**

**Step 1:** Go to **Tools → Automations** from the left navigation panel

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

**Step 2:** Click on **‘Create New’**

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

**Step 3:** Name your automation and click on **Create**&#x20;

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

**Step 4:** Start by selecting the source object. You can choose to build an automation on

* segment (account, developer, buyer)
* or a list (account, developer)

Then, click on ‘Save and next’

In this example, we'll build the automation on an account segment

<figure><img src="/files/1nNpvVHsnoH6u18LYGHj" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Note: You can build an automation only on your owned segments i.e segments created by you.
{% endhint %}

**Step 5:** Once you’ve selected the source, you can choose the trigger that will fire this automation. For every segment type and list there’s a pre-defined list of triggers from which you can select.

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

**Account Segment**

| Trigger                                    | What it means                                          |
| ------------------------------------------ | ------------------------------------------------------ |
| New Account added to the segment           | New account is added to the segment                    |
| New Activity in an account in a segment    | New activity is detected in any account in the segment |
| New Buyer added to an account in a segment | A new buyer is added to an account in the segment      |
| Surge in Activity                          | An account showing recent spike in activity            |
| Key Page Visited                           | Account shows activity on any of the key pages         |
| Change in Developer Funnel Stage           | Account moves to a new developer funnel stage          |

**Developer Segment**

| Trigger                          | What it means                                                         |
| -------------------------------- | --------------------------------------------------------------------- |
| New Developer added to a segment | New developer is added to the segment                                 |
| New Activity in the segment      | New activity done by any developer in the segment                     |
| Key Page Visited                 | Any developer from the segment shows activity on any of the key pages |

**Buyer segment**

| Trigger                      | What it means                                                     |
| ---------------------------- | ----------------------------------------------------------------- |
| New Buyer added to a segment | New buyer is added to the segment                                 |
| New Activity in the segment  | New activity is done by any buyer in the segment                  |
| Key Page Visited             | Any buyer from the segment shows activity on any of the key pages |

**Account list**

| Trigger                          | What it means                                          |
| -------------------------------- | ------------------------------------------------------ |
| New Activity in an account       | New activity is detected within an account in the list |
| New Buyer added to an account    | New buyer added to an account in the list              |
| Surge in Activity                | An account showing recent spike in activity            |
| Key Page Visited                 | Account shows activity on any of the key pages         |
| Change in Developer Funnel Stage | Account moves to a new developer funnel stage          |

**Developer list**

| Trigger                                 | What it means                                |
| --------------------------------------- | -------------------------------------------- |
| New Activity by a developer in the list | New developer activity detected              |
| Key Page Visited                        | Developer engaging with any of the key pages |

Then, click on save and next

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

**Step 6:** Once you’ve selected a trigger, you can choose to add conditions that need to be met for an automation to trigger. This is an optional step. (Choose the skip this step option to move to the next step).

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

Here’s a list of filters you can choose as conditions:

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

In this example - we’ve added the following conditions - Activity type: Github - Fork, AND Designation: CXO/Founder/VP/Director

Once done, click on save and next

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

**Step 7:** You can choose to send this data either to Zapier via webhooks or to your slack channel/DM.

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

* **Send to Zapier via webhook**: Choose the webhook you want to map this data to. [Here’s a guide on creating webhooks.](https://docs.reo.dev/integrations/webhooks)

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

* **Get alerts via Slack:** Choose to get alerts on slack either on DM or a specific channel.

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

Click on ‘**save and publish’** to activate the automation

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

### **Managing Automations**

You can see all the automations you’ve created under the automations section.

1. The target object column shows where the data is being sent.

<figure><img src="/files/5LBblVOAA55yvp8UQzCB" alt=""><figcaption></figcaption></figure>

2. Status shows whether an automation is active/inactive or in draft

<figure><img src="/files/3pYFLEZ1DRJzFJJIVXq7" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Note: If an active automation is edited and no source is selected, the automation will be moved to ‘draft’ status automatically.
{% endhint %}

3. **Under actions** -

* Click on view to see the automations criteria.&#x20;
* To edit an existing automation you can simply click on edit. If you edit any one of the steps in the automation, the subsequent steps will need to be re-configured.
* Click on play/pause icon to Activate/Deactivate an automation

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

* Click on the 3 dotted menu to:
  * Rename it
  * Copy automation ID
  * Delete an automation (Quick note: Active automations can’t be deleted directly. To do so, first de-activate the automation and then delete.)

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


---

# Agent Instructions: 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:

```
GET https://docs.reo.dev/automations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.