Reo.Dev Zapier Integration Guide

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.

Step 1: Click on Accept and Build a Zap.

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

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

Step 4: Search for the Reo.Dev app.

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.

Once you've selected the trigger, click Continue.

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 Settings → Integrations → API Keys.

2. Locate the Product Export & Zapier Integration section.

3. Click Copy to use the key, or Re-generate if needed.

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

Step 7: Click Continue to complete the Setup.

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

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

Metadata You’ll Receive

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

Account Fields

Developer Fields

Buyer Fields

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

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.