Connecting Reo.dev

Overview

Reo.dev connects two ways at once:

• Outbound — once you turn on Sync your accounts to Reo.dev, TrailSpark keeps a list called Trailspark Accounts in your Reo.dev account, made up of your eligible accounts. This gives Reo.dev the accounts you actually track, so it can watch them for developer activity instead of only whatever it already happens to have.
• Inbound — once you build a Reo.dev segment from that list and select it under What syncs, TrailSpark checks that segment about once a day and matches what it finds — developer buying-intent signals and company details — against accounts you already track.

The Connect screen collects everything it needs up front — your API key, plus (optionally) the Product Usage API key and your Reo.dev login email — so turning on account sync is usually just confirming how many accounts it'll add. Skip those optional fields at connect time and TrailSpark asks for them again the moment you turn on account sync, so setup is still a single sitting either way, and runs the first push immediately rather than waiting for a scheduled sync.

Unlike Clay, there's no callback to set up on Reo.dev's side for the inbound leg; the pull runs entirely from the TrailSpark side. Both legs are credit-free — TrailSpark never triggers Reo.dev's paid enrichment.

Before you start (in Reo.dev)

Sign in to Reo.dev and go to Configurations > API Keys to generate an API key. You'll need an admin role in your Reo.dev account to create one.

While you're there, you can also copy your Product Usage API key from the same page. TrailSpark's Connect screen asks for it — along with your Reo.dev login email — up front, so account sync is ready to turn on right away. Both are optional: skip them now and TrailSpark asks for the Product Usage key again when you turn on account sync.

Step 1: Connect

Go to Settings > Integrations, find Reo.dev in the Data enrichment section, and click Configure.

• Connection name — a label for this connection (e.g., "Reo.dev production")
• API key — paste the key you generated in Reo.dev. It's stored securely and never shown again.
• Product Usage API key (optional) — paste the key from the same Configurations > API Keys page in Reo.dev. This is what TrailSpark uses to keep your account list up to date in Reo.dev. You can add it later instead, from the Sync your accounts to Reo.dev card, when you turn on account sync.
• Your Reo.dev login email (optional) — the account list TrailSpark builds is created under this Reo.dev user, so it shows up in your My Lists and you can share it with your team from there. You can add this later too.

Click Connect.

If you paste a Product Usage API key that Reo.dev doesn't recognize, TrailSpark still completes the connection — it just lets you know the sync key was rejected, so you can update it when you turn on account sync in Step 2.

Step 2: Turn on "Sync your accounts to Reo.dev"

Once connected, open the Enrichment rules tab. It now opens with a Sync your accounts to Reo.dev card — this is the outbound leg.

Flip Turn on account sync.

If you gave TrailSpark a Product Usage API key when you connected, you'll go straight to a confirmation: how many accounts it will add to the Reo.dev list (an approximate count), and a note that this doesn't use your Reo.dev credits. Confirm with Turn on sync.

If you skipped that field at connect (or Reo.dev rejected it), a Connect your sync key step appears first instead, asking for the same two fields from Step 1:

• Product Usage API key — paste the key from Reo.dev → Settings > Configurations > API Keys (you'll need admin access).
• Your Reo.dev login email — the account list TrailSpark builds is created under this Reo.dev user, so it shows up in your My Lists, and you can share it with your team from there.

TrailSpark checks the key with Reo.dev immediately. If Reo.dev rejects it, you'll see that right on the spot — check it's the Product Usage key (not the key from Step 1) and try again. Once it's accepted, click Save and continue, then you'll land on the same confirmation described above.

The first push runs right away — you don't wait for a scheduled sync. When it finishes, the card shows: "Pushed N accounts — the 'Trailspark Accounts' list is ready in Reo.dev." (If a sync happens to already be running, you'll instead see a note that it's finishing in the background — check back in a minute.)

Once it's on, the card also offers Include company name alongside the domain (off by default). The domain is always sent — it's how Reo.dev matches the account — turning this on additionally sends the account's company name.

After the push

Once the first push succeeds, the card shows a highlighted prompt right underneath: "Next: in Reo.dev, create a segment from the 'Trailspark Accounts' list, then select it below under What syncs.", with a Refresh segments button next to it.

Create the segment in Reo.dev (see Step 4 below), come back to TrailSpark, and click Refresh segments — your new segment shows up in the What syncs list further down the page, with no page reload needed. This prompt stays on screen until you select a segment there; once you do, it's replaced by the normal sync-status line.

Step 3: Choose which accounts sync (optional)

Below the card, a Which accounts sync section uses the same rule builder as ICP eligibility, applied to a different question: not "which ICP does this account belong to," but "does this account get pushed to Reo.dev." The guidance on the page explains the default: "Leave empty to sync every account with a business domain."

Leave it empty to push every eligible account, or add rules to narrow the list — for example, to only accounts currently on a trial. Click Save criteria when you're done. The account-sync card above shows a one-line summary of whatever you've saved here, next to Which accounts sync.

Step 4: Finish setup in Reo.dev

The account-sync card includes a Set up in Reo.dev checklist:

1. Turn on account sync (connecting your sync key too, if you didn't already at connect) — done in Step 2.
2. In Reo.dev: My Lists → share the Trailspark Accounts list with your team (optional) and create a segment from it. This is a one-time step you do in your Reo.dev dashboard, not in TrailSpark.
3. Select that segment in the section below (Step 5).

The card also notes the one real constraint on this whole feature: Reo.dev returns signals only for accounts where it observes developer activity. Pushing your accounts into the Trailspark Accounts list maximizes the chance Reo.dev has something to say about them — it doesn't guarantee a match for every account.

Step 5: Choose your segment(s) under "What syncs"

Further down the same Enrichment rules tab, a What syncs section shows: "Choose which Reo.dev segments to sync. Accounts you don't already track are ignored."

Check the box next to the segment you built from the Trailspark Accounts list in Step 4 — and any other Reo.dev segment you want pulled in, such as one tracking hiring signals. Click Save, then confirm. The confirmation step tells you plainly what you're about to turn on: "Reo.dev syncs the accounts in your selected segments: [segment names]." plus "Only accounts you already track in Trailspark are updated — nothing new is ever created."

If nothing is checked, TrailSpark shows a warning right in the What syncs section — and again in the confirmation step — instead of a rule count or credit estimate: "No segments selected — nothing will sync until you choose at least one." You can still save with nothing selected, but nothing will sync back until you come back and check at least one segment. This is independent of account sync — you can push accounts to Reo.dev in Step 2 without pulling anything back yet.

Step 6: Watch the sync status

Two status lines cover the two directions:

• Outbound — on the Sync your accounts to Reo.dev card, once accounts have been pushed: "N accounts synced · last sync [time ago]." While account sync is on, the card also states plainly: "Accounts are only added, never removed automatically — remove accounts in Reo.dev if needed." If a push fails, the card shows the error as-is underneath the status line.
• Inbound — back on the Connection tab, a Sync status section shows where the daily pull stands:
  • Before the first sync (with at least one segment selected): "Waiting for the first sync."
  • After a sync runs: "Last synced [time ago] — N accounts checked, M matched."

"Checked" is how many accounts in your selected segments Reo.dev reviewed; "matched" is how many of those it was able to connect to an account you already track in TrailSpark. Unmatched accounts are dropped, not saved — Reo.dev never adds a new account or lead to your workspace.

If your sync key stops working

If the Product Usage key you saved in Step 2 later stops working — for example, you rotated it in Reo.dev — the Sync your accounts to Reo.dev card shows the same prompt again: "Reo.dev rejected the sync key. Paste your Product Usage API key (Reo.dev → Settings → Configurations → API Keys)."

Sign in to Reo.dev, go to Settings > Configurations > API Keys (admin access required), copy a current Product Usage API key, paste it into the field on the card along with your login email, and click Save key. TrailSpark saves it against this same connection and retries the push right away — you can also click Retry sync now any time. Your API key from Step 1 keeps working for the daily pull throughout; nothing else about the connection changes.

After you're connected

The connection page shows "Reo.dev is connected." Your API key is saved securely and never shown again — to replace it, disconnect and reconnect.

• Test connection verifies TrailSpark can reach Reo.dev with your key.
• Disconnect stops both the daily push and the daily pull. Reconnect, turn account sync back on, and re-select your segments to resume.

Next Steps

• Third-Party Intent & Field Provenance — how Reo.dev's intent is labeled and never drives a score alone
• Connecting Clay — add a second enrichment source, with its own rules and budget caps