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.

Create an automation:

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

Step 2: Click on ‘Create an Automation’

Step 3: Name your automation and click on Create New.

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 & next’

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

Note: You can build an automation only on your owned segments i.e segments created by you.

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.

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

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

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

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.

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

• Send to Zapier via webhook: Choose the webhook you want to map this data to. Here’s a guide on creating webhooks.

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

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

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.

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

Note: If an active automation is edited and no source is selected, the automation will be moved to ‘draft’ status automatically.

1. Under the stats column you can see the total number of times an automation has run - number of successful and failed runs.

1. Under actions - you can click on view to see the automations criteria. 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.

1. Click on the 3 dotted menu to:

   1. Activate an automation

   2. Delete an automation (Quick note: Active automations can’t be deleted directly. To do so, first de-activate the automation and then delete.)

   3. Rename it

   4. Copy automation ID