Outreach

Datafly Signal delivers identified events to Outreach server-to-server, creating Prospect records from your website and product activity. Marketing- and product-sourced leads flow straight into your sales team’s sequences with no client-side form integration.

Prerequisites

Before configuring Outreach in Signal, you need an Outreach account with admin access and a connected OAuth application.

Step 1: Create an Outreach Connected Application

1. Sign in to the Outreach Developer Portal.
2. Go to My Apps and click Create New App.
3. Give the app a name (e.g. “Datafly Signal”).
4. Under OAuth, set a Redirect URI you control (used once to mint the refresh token).
5. Under Scopes, enable:
   • prospects.read
   • prospects.write
6. Save the app and note the Identifier (client ID) and Secret (client secret).

Step 2: Obtain a Refresh Token

Outreach does not support the client_credentials grant, so you authorise the app once via the authorization_code flow and store the resulting refresh token.

https://api.outreach.io/oauth/authorize?client_id=YOUR_CLIENT_ID&redirect_uri=YOUR_REDIRECT_URI&response_type=code&scope=prospects.read+prospects.write

curl -X POST https://api.outreach.io/oauth/token \
  -d client_id=YOUR_CLIENT_ID \
  -d client_secret=YOUR_CLIENT_SECRET \
  -d redirect_uri=YOUR_REDIRECT_URI \
  -d grant_type=authorization_code \
  -d code=THE_CODE

Configure in Signal

Configuration Fields

Setup

1. Go to Integrations > Add Integration > Outreach.
2. Choose the Lead Capture preset.
3. Enter your client_id, client_secret, and refresh_token.
4. Select the consent categories that should gate delivery (typically marketing). Signal only forwards events from consenting, identified users.
5. Click Save.

API Endpoint

POST https://api.outreach.io/api/v2/prospects
Authorization: Bearer {access_token}
Content-Type: application/vnd.api+json

Signal exchanges your refresh token for a short-lived access token and sends it in the Authorization header. The request body is a JSON:API document. The application/vnd.api+json media type is required — Outreach rejects requests without it.

Identity Signals

Outreach is a first-party CRM that stores the real, contactable prospect. Identity data is sent in the clear (not hashed) — the email address is Outreach’s dedupe key, and a hashed value would be unusable to a salesperson.

How to send identity data

Call datafly.identify() when a user submits a form, signs up, or requests a demo, then track() the event:

datafly.identify("user-123", {
  email: "jane.doe@acme.com",
  firstName: "Jane",
  lastName: "Doe",
  company: "Acme Inc",
  title: "Head of Growth",
  phone: "+44 7700 900123",
  city: "London",
  country: "GB"
});

Event Mapping

Only identity-bearing events create prospects. Every other event is dropped (defaults.action: drop).

Lead Capture preset

Example: Demo Requested

Datafly.js call:

datafly.identify("user-123", {
  email: "jane.doe@acme.com",
  firstName: "Jane",
  lastName: "Doe",
  company: "Acme Inc",
  title: "Head of Growth",
  phone: "+44 7700 900123"
});
 
datafly.track("Demo Requested");

Outreach payload sent by Signal:

{
  "data": {
    "type": "prospect",
    "attributes": {
      "emails": ["jane.doe@acme.com"],
      "firstName": "Jane",
      "lastName": "Doe",
      "name": "Jane Doe",
      "title": "Head of Growth",
      "occupation": "Head of Growth",
      "company": "Acme Inc",
      "mobilePhones": ["+447700900123"],
      "tags": ["Signal", "demo-request"]
    }
  }
}

Outreach responds with the created prospect, including its assigned id, createdAt, and the echoed attributes.

Testing Your Integration

1. Trigger a tracked event on your site (e.g. submit a demo-request form) as an identified, consenting user.
2. In Outreach, go to Prospects and search for the email address you used.
3. The new prospect should appear within seconds, carrying the name, company, phone, and Signal tag.
4. Use Signal’s Event Debugger to inspect the exact JSON:API document sent and the Outreach response code.

Troubleshooting

Rate Limits

Outreach enforces a per-token request ceiling (surfaced via X-RateLimit-* response headers). Signal applies a conservative client-side rate limit and retries 429 responses with backoff, so normal lead volumes deliver without manual tuning.