# Zapier

The **Reo.Dev x Zapier** integration lets you build automated workflows by syncing accounts, developers, and buyers from your Reo.Dev segments to any of the 5,000+ apps supported by Zapier.

Refer to the section below to find out how to connect your Reo.Dev instance to your Zapier account.

{% hint style="info" %}
**Note:** Currently Reo.Dev is an **Invite only** app on Zapier. Use this [link](https://zapier.com/developer/public-invite/204690/3b325508b5ee65407eb1f8c990e7671f/) to connect the Reo.Dev app
{% endhint %}

**Step 1:** Click on **Accept and Build a Zap**.

![](https://usercontent.us.prod.clueso.io/d06f019c-da0b-4d5b-9fdd-9630e7fd5d0f/e2438d2b-17f7-44bf-8e64-a12a2a849532/3f189dad-c58b-4ef5-9eab-abdf422ab6c4/images/502a8167-a551-4a08-9c52-0c46dd9151b9.png)

**Step 2:** You’ll be redirected to the Zapier webpage. Here, click **Create** and then click **New Zap**.

![](https://usercontent.us.prod.clueso.io/d06f019c-da0b-4d5b-9fdd-9630e7fd5d0f/e2438d2b-17f7-44bf-8e64-a12a2a849532/3f189dad-c58b-4ef5-9eab-abdf422ab6c4/images/ca8fc1bf-4735-47e6-a76d-6b768456b1c0.png)

**Step 3:** Click on the Trigger panel to first add and authenticate the Reo.Dev app

![](https://usercontent.us.prod.clueso.io/d06f019c-da0b-4d5b-9fdd-9630e7fd5d0f/e2438d2b-17f7-44bf-8e64-a12a2a849532/3f189dad-c58b-4ef5-9eab-abdf422ab6c4/images/73cb6c73-f13d-4d48-a9c8-752fce8f5e36.png)

**Step 4:** Search for the Reo.Dev app.

![](https://usercontent.us.prod.clueso.io/d06f019c-da0b-4d5b-9fdd-9630e7fd5d0f/e2438d2b-17f7-44bf-8e64-a12a2a849532/3f189dad-c58b-4ef5-9eab-abdf422ab6c4/images/66ae4539-0922-45e5-b7fb-8ccfffbfcda4.png)

### Choose a Trigger Event

**Step 5:** In this step, you’ll select the event in Reo.Dev that will trigger the Zap.

#### **Supported Triggers**

These are **polling-based** triggers. Zapier checks for new entries every 15 minutes.

| **Trigger**                           | **Description**                                    |
| ------------------------------------- | -------------------------------------------------- |
| **Get Accounts from Account Segment** | Pulls accounts from a selected account segment     |
| **Get Developers from Dev Segment**   | Pulls developers from a selected developer segment |
| **Get Buyers from Buyer Segment**     | Pulls buyers from a selected buyer segment         |

Once you've selected the trigger, click **Continue**.

![](https://usercontent.us.prod.clueso.io/d06f019c-da0b-4d5b-9fdd-9630e7fd5d0f/e2438d2b-17f7-44bf-8e64-a12a2a849532/3f189dad-c58b-4ef5-9eab-abdf422ab6c4/images/f45bc8c3-505e-46c2-a8c0-0debd1aa1745.png)

***

**Step 6:** Connect Your Reo.Dev Account

Next, you’ll be prompted to authenticate your Reo.Dev account.

Click **Select Account**, then click **Connect a new account**. This will open a screen asking for your **Reo.Dev API Key**.

**To access your API key:**

1. Navigate to **Configurations → API Keys**.
2. Locate the **Product Export & Zapier Integration** section.
3. Click **Copy** to use the key, or **Re-generate** if needed.

![](https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FJaMDprKRB9aMYpGRzaoi%2FScreenshot%202026-03-11%20at%204.38.56%20PM.png?alt=media\&token=822aa3d6-ef20-4920-b03b-dddc472fb322)

{% hint style="info" %}
**Note:** Only **Admin** users in Reo.Dev have permission to generate API keys. Other users can still view and copy an existing key.
{% endhint %}

Paste the key into the Zapier prompt and click **Yes, Continue to Reo.Dev (2.0.0)**.

![](https://usercontent.us.prod.clueso.io/d06f019c-da0b-4d5b-9fdd-9630e7fd5d0f/e2438d2b-17f7-44bf-8e64-a12a2a849532/3f189dad-c58b-4ef5-9eab-abdf422ab6c4/images/621835a9-5145-4773-bf7b-c1ceba774d37.png)

**Step 7:** Click **Continue** to complete the Setup.

![](https://usercontent.us.prod.clueso.io/d06f019c-da0b-4d5b-9fdd-9630e7fd5d0f/e2438d2b-17f7-44bf-8e64-a12a2a849532/3f189dad-c58b-4ef5-9eab-abdf422ab6c4/images/e94182fa-1836-4be2-9901-c7ab55bc7967.png)

**Step 8:** Select the segments you’ve created from which you want data to flow to trigger the Zap and click **Continue**.

![](https://usercontent.us.prod.clueso.io/d06f019c-da0b-4d5b-9fdd-9630e7fd5d0f/e2438d2b-17f7-44bf-8e64-a12a2a849532/3f189dad-c58b-4ef5-9eab-abdf422ab6c4/images/355f99e3-5bfb-4326-985a-218a62f629d3.png)

**Step 9:** Zapier allows you to test whether the data from the selected segment is flowing correctly.

![](https://usercontent.us.prod.clueso.io/d06f019c-da0b-4d5b-9fdd-9630e7fd5d0f/e2438d2b-17f7-44bf-8e64-a12a2a849532/3f189dad-c58b-4ef5-9eab-abdf422ab6c4/images/bc81e8d7-1e82-4eb1-a543-e5f22f11b521.png)

***

### Metadata You’ll Receive

Each Zap triggered by Reo.Dev includes detailed metadata. Below are the fields returned for each entity:

#### Account Fields

| **Field**                | **Example**                                                                                            |
| ------------------------ | ------------------------------------------------------------------------------------------------------ |
| Org ID                   | `814bf44a-e0a0-49a6-abb6-3017d6f3a9df`                                                                 |
| Country                  | United States                                                                                          |
| Account Name             | Acme Co.                                                                                               |
| Account Domain           | acme.com                                                                                               |
| Active Developers Count  | `3`                                                                                                    |
| Developer Activity Score | `LOW`                                                                                                  |
| Customer Fit Score       | `MODERATE`                                                                                             |
| First Activity Date      | `2024-12-09`                                                                                           |
| Last Activity Date       | `2025-05-15`                                                                                           |
| Tags                     | `Competitor Repo - Open Issues, LangChain Integration, NLP Models`                                     |
| Activity Score           | `HIGH`                                                                                                 |
| Activity Score Numeric   | 70                                                                                                     |
| City                     | San Francisco                                                                                          |
| State                    | California                                                                                             |
| Developer Funnel         | `DISCOVER`                                                                                             |
| Reo Account Link         | <https://web.reo.dev/dashboard/accounts?orgId=03e19e88-5b3e-4f58-b21b-aa7d737d8d19&activeKey=Overview> |

![](https://usercontent.us.prod.clueso.io/d06f019c-da0b-4d5b-9fdd-9630e7fd5d0f/e2438d2b-17f7-44bf-8e64-a12a2a849532/3f189dad-c58b-4ef5-9eab-abdf422ab6c4/images/b0734407-bcea-4c3b-b79a-e4f4c4d2cdc8.png)

***

#### Developer Fields

| Field                    | Example                                                                               |
| ------------------------ | ------------------------------------------------------------------------------------- |
| Developer ID             | `1146c672-c0b3-4161-82dd-be32e58be6df`                                                |
| Developer Org ID         | `6227136f-49bd-4956-bd67-d6b6cec0129c`                                                |
| Developer Name           | John Doe                                                                              |
| Developer LinkedIn       | LinkedIn URL                                                                          |
| Developer GitHub         | GitHub URL                                                                            |
| Developer Business Email | <example@email.com>                                                                   |
| First Activity Date      | `2025-03-28 15:54:03`                                                                 |
| Last Activity Date       | `2025-05-17 17:13:24`                                                                 |
| Tags                     | `Checked Playbook, Product Login`                                                     |
| Activity Score           | `HIGH`                                                                                |
| Activity Score Numeric   | 70                                                                                    |
| Developer Designation    | Software Engineer                                                                     |
| Reo Developer Link       | <https://web.reo.dev/dashboard/developers?devId=e2eb4d5c-a1f8-40ff-a50a-dc088ec99600> |
| State                    | California                                                                            |
| City                     | San Francisco                                                                         |

![](https://usercontent.us.prod.clueso.io/d06f019c-da0b-4d5b-9fdd-9630e7fd5d0f/e2438d2b-17f7-44bf-8e64-a12a2a849532/3f189dad-c58b-4ef5-9eab-abdf422ab6c4/images/8a2040ab-cb0b-4c12-bb20-f06ae0205a83.png)

***

#### Buyer Fields

| Field                     | Example                                |
| ------------------------- | -------------------------------------- |
| Buyer ID                  | `ec4ab44e-79d1-41db-89d8-2bd9b3da7143` |
| Buyer Org ID              | `80714138-2587-4714-8aae-869a060557ef` |
| Buyer Name                | `John Doe`                             |
| Buyer LinkedIn            | LinkedIn URL                           |
| Buyer GitHub              | GitHub URL                             |
| Buyer Email               | <example@email.com>                    |
| Buyer First Activity Date | `2024-10-01 01:43:39`                  |
| Buyer Last Activity Date  | `2025-05-17 17:35:00`                  |
| Tags                      | `Buyer tag`                            |

![](https://usercontent.us.prod.clueso.io/d06f019c-da0b-4d5b-9fdd-9630e7fd5d0f/e2438d2b-17f7-44bf-8e64-a12a2a849532/3f189dad-c58b-4ef5-9eab-abdf422ab6c4/images/7507b663-ba83-473b-8631-7b8d99d4908b.png)

***

### Understanding Zap Behavior: Net New Data Only

By default, the Reo.Dev Zapier integration only triggers when a **new account, developer or buyer is added to a segment**. This means:

* The Zap **does not backfill** historical data already present in the segment at the time the Zap is turned on.
* Only **net new entries** to the segment (after the Zap is active) will trigger and be sent to the connected app.

#### Why This Matters

If your Reo.Dev segment already includes a large set of accounts or developers (e.g., 3000+), Zapier will not push those existing records to your connected app (e.g., LinkedIn Ads, Apollo.io, etc.). You’ll only see new entries added **after** the Zap is live.

***

### Recommended Best Practice: Upload Historical Data via CSV

![](https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FyMVhCreDdmpElDBClEuK%2FScreenshot%202026-03-11%20at%204.07.43%20PM.png?alt=media\&token=e041a56c-4b3f-4d82-ad71-83ba47ca6527)

If your use case requires **all existing segment data** (not just new additions) to be sent through Zapier, follow these steps:

#### How to Backfill Using CSV Upload

1. **Export the data** from your existing Reo.Dev segment as a CSV file.
2. **Re-upload the CSV** to your platform (e.g. LinkedIn Ads, Salesloft, etc.) using native import functionality or a separate Zap that processes CSV rows.
3. **Then activate the Zap**, so future additions to the segment are automatically handled.

This hybrid approach ensures:

* You don’t miss out on historical data.
* Zapier picks up only net new entries going forward—keeping workflows efficient and lightweight.