Add Buyer Contacts as LinkedIn Connections on Autopilot for your Sales Reps

• Introduction

• How the data flows out of Reo.Dev

• Step 1: Set up your Buyer Segment or Buyer Audience

• Step 2: Set up the Data Out Integration

• Step 3: Workflow Automation Example using Phantombuster

• Step 4: Assign buyer lists to specific rep handles

• 10x Workflow ideas to run with this

Resources:

• https://docs.reo.dev/integrations/webhooks

• https://www.reo.dev/playbook/data-transfer-guide-reo-la-growth-machine

📌 Need help at any point? If you need support implementing this playbook end to end, contact your Account Manager or write to us at [e-mail].

Introduction

Your AEs and SDRs spend hours manually searching LinkedIn for the right buyers at the right accounts. This playbook eliminates that entirely. Once you have a live Buyer Segment or Buyer Audience in Reo.Dev, you can pipe those contacts directly into any LinkedIn automation tool and build a continuously growing network of your most valuable prospects, without anyone lifting a finger.

The end goal is more than just connections. When you combine this with an active LinkedIn content strategy across your AE, SDR, and Founder handles, you engineer a situation where your key buyers see your content consistently in their feed. That increases brand familiarity, warms up outbound, and has a measurable positive effect on LinkedIn ad conversions as well. You are, in effect, owning the LinkedIn feed of your ICP.

Before setting this up, make sure you have your buyer contacts ready. If you have not done that yet, follow the Upload Target Accounts & Get Buyer Contacts playbook first to build your Buyer Segment or Buyer Audience.

How the data flows out of Reo.Dev

The options available to you depend on whether you are working with a Buyer Segment or a Buyer Audience.

If you are using a Buyer Segment, you have three options:

Option 1: Native Zapier integration (recommended for an ongoing workflow)

Reo.Dev integrates with Zapier natively. Using the "Get Buyers from Buyer Segment" trigger, Zapier polls your Buyer Segment every 15 minutes and sends any new buyer contacts downstream to your tool of choice. This keeps your LinkedIn automation campaigns live and self-updating as new buyers enter the segment. Once it is set up, you do not need to touch anything.

✏️ Note: Reo.Dev is currently an invite-only app on Zapier. Use this invite link to connect the Reo.Dev app before building your Zap.

Option 2: Webhooks (for Zapier, n8n, Make, Clay, or any webhook-compatible tool)

Reo.Dev Webhooks support Buyer Segments directly. Go to Settings → Integrations → Webhooks, create a new webhook with a Developer or Buyer payload type, and point the destination URL to your tool's catch endpoint.

Once mapped to your Buyer Segment, any new buyer added to the segment will be pushed automatically. This is the right path if you prefer n8n, Make, or Clay over the native Zapier integration.

Option 3: CSV export (for one-time or periodic uploads)

From any Buyer Segment, you can download the full contact list as a CSV. The export includes each buyer's LinkedIn URL, email, name, title, company, and any tags assigned in Reo.Dev.

Upload this directly into your LinkedIn automation tool to launch a campaign immediately. This is the simplest route if you want to move fast on a static list without setting up an integration.

If you are using a Buyer Audience, you have two options:

Option 1: Webhooks Reo.Dev Webhooks also support Buyer Audiences. The setup is identical to the Buyer Segment webhook path above. Go to Settings → Integrations → Webhooks, create your webhook, and map it to the Buyer Audience. New buyers added to the audience will be pushed automatically to your downstream tool.

Option 2: CSV export Download the full buyer list as a CSV from the Audiences panel and upload it into your LinkedIn automation tool of choice. Since Buyer Audiences do not have a native Zapier trigger, this is the right static option if you are not using webhooks.

Step 1: Set up your Buyer Segment or Buyer Audience

Refer to this playbook for this step: Upload Target Accounts & Get Buyer Contacts

Step 2: Set up the Data Out Integration

Path A: Zapier (Buyer Segment only)

In Zapier, create a new Zap. Set the app to Reo.Dev (2.0.0) and the trigger event to "Get Buyers from Buyer Segment". Connect your Reo.Dev account using your API key from Settings → Integrations → API Keys. Select your Buyer Segment and test the trigger to confirm buyer records are coming through. Each record will include the buyer's name, LinkedIn URL, email, title, and account name.

Add an optional Formatter step (Text → Split Text, separator: space) to extract the first name cleanly for personalized outreach messaging downstream.

Set the action step to your LinkedIn automation tool of choice. Map the LinkedIn URL field from Reo.Dev to the connection or lead field in the tool. Publish the Zap.

Full guide: Reo.Dev Zapier Integration Guide

Path B: Webhooks (Buyer Segment or Buyer Audience)

In Reo.Dev, go to Settings → Integrations → Webhooks. Click Create Webhook, give it a descriptive name, select the appropriate payload type, and paste your tool's catch URL as the destination. Once created, map the webhook to your Buyer Segment or Buyer Audience. All existing buyers in the segment or audience will be sent on the first sync. After that, only net-new additions will trigger the webhook.

Full guide: Webhooks in Reo.Dev

Path C: CSV export (Buyer Segment or Buyer Audience)

From the Segments or Audiences panel, open the three-dot menu on your Buyer Segment or Buyer Audience and select the CSV download option. Upload the file directly into your LinkedIn automation tool to launch your campaign. Re-download and re-upload periodically to keep the list current if you are not using a live integration.

Step 3: Workflow Automation Example using Phantombuster

Phantombuster is well suited for LinkedIn connection campaigns at scale. Here is how you connect it to your Reo.Dev buyer data.

If using Path C (CSV): In Phantombuster, navigate to the LinkedIn Network Booster phantom. Upload your Reo.Dev buyer CSV export as the input source. Map the LinkedIn URL column to the phantom's LinkedIn profile URL field. Set your daily connection limit (LinkedIn's safe threshold is typically 20 to 30 connection requests per day per account) and configure your connection request message if you want to include one. Launch the phantom.

If using Path A or B (Zapier or Webhooks): In your Zap or webhook pipeline, set the action step to Phantombuster. Use the "Add Value to a Phantom" action and select your LinkedIn Network Booster phantom as the target. Map the buyer's LinkedIn URL from Reo.Dev to the phantom's input argument. Each time a new buyer enters your Reo.Dev segment or audience, they will be automatically queued into Phantombuster for outreach.

Other tools that work with the same pattern: LGM (LaGrowthMachine), Heyreach, Dripify, Meet Alfred, Lemlist, Dux-Soup. The action step and field mapping will differ slightly per tool, but the upstream logic from Reo.Dev is identical across all of them.

Step 4: Assign buyer lists to specific rep handles

One of the more powerful configurations here is mapping buyer contacts to individual rep LinkedIn handles rather than running everything from a single account.

AE-level assignment: Build a Buyer Segment scoped to each AE's assigned accounts using the CRM Owner filter. For example, create a segment where CRM Account Owner includes [AE Name] and apply your buyer persona filters. That AE's LinkedIn handle gets connected to that segment in your LinkedIn automation tool. Their profile sends connection requests only to buyers from their own book of business.

Multi-handle campaigns: If you want to run campaigns from multiple handles simultaneously, for example all AE profiles connecting with buyers from their respective lists, build one segment per AE, one Zap or webhook per segment, and one phantom or campaign per rep. This scales cleanly once the template is set.

Founder and executive handles: The same setup applies for Founder, CEO, or VP handles. Build a Buyer Segment filtered to your highest-priority ICP accounts and connect it to those profiles. Buyers receiving connection requests from a Founder will accept at a materially higher rate than from an SDR.

10x Workflow ideas to run with this

Build a LinkedIn echo chamber for your ICP. When all your AE, SDR, and Founder handles are connected to the same pool of buyers, your content starts appearing in those buyers' feeds from multiple directions. They see your product, your use cases, and your team consistently. By the time an SDR reaches out cold, you are not cold anymore.

Run warm LinkedIn nurture before outbound email. Send connection requests first. Wait for acceptance. Then trigger your SDR's outreach sequence. Response rates are materially higher when the prospect already recognizes the name.

Amplify reach with LinkedIn ads by targeting the accounts your buyers belong to. LinkedIn contact-level audience matching has notoriously low match rates, so targeting individual LinkedIn handles is not the right approach here. The more effective play is to sync your high-intent account segments from Reo.Dev directly to LinkedIn Campaign Manager as company-level audiences. When you target at the account level, you reach all relevant decision-makers within those companies, including your buyers, without relying on contact matching.

If you are using HubSpot, this workflow is already mapped out: sync your Reo.Dev account segments to HubSpot and create a LinkedIn Matched Audience from there.

This lets you serve ads to exactly the companies already showing developer intent or product engagement signals. See the full guide: Sync Reo.Dev Segments to HubSpot and Run LinkedIn Ads.

Prioritize high-intent buyers for immediate outreach. In Reo.Dev, buyers identified through developer activity signals (tagged as Dev Activity source in your Buyer Segment) are the hottest contacts to route to your fastest-moving SDRs rather than passive nurture queues.

Best practices

Set a conservative daily connection limit per LinkedIn account. Sending more than 25 to 30 connection requests per day per account is generally considered risky for account health. Most tools let you configure this at the campaign or phantom level.

Write a short, specific connection request note. Generic notes get ignored. Reference the account's product category or a relevant signal, for example: "We work with a lot of companies building developer tooling in your space, would love to connect."

Rotate across multiple handles when targeting the same company. Do not have multiple people from your team sending connection requests to the same buyer on the same day.

Refresh your list regularly. If you have auto-refresh enabled on your Buyer Segment, new buyers are added automatically and will flow into your pipeline without manual intervention. For Buyer Audiences on the CSV path, re-download and re-upload periodically to keep the campaign list current.