Outreach

Outreach is a sales engagement platform. Datafly Signal creates prospects in Outreach server-side (REST API v2, JSON:API POST /api/v2/prospects) when a visitor submits a lead form, requests a demo or signs up, so web leads reach sales sequences without a form integration.

Why route Outreach through Datafly Signal

• Records come from your server, not the browser. They reach Outreach even when a tracker blocker or a failed page unload would have dropped a client-side call, and no form integration or browser tag is needed.
• Delivery is queued and retried. Signal buffers to Kafka and retries on 429 or a transient failure rather than dropping the event; a permanent rejection goes to the dead-letter queue with the vendor’s reason.
• One consent decision governs every destination. Outreach is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.

Get your Outreach credentials

Configuration

Management UI setup

1. Go to Integrations in the sidebar and open the Integration Library tab.
2. Find Outreach under CRM and click Install.
3. Choose a preset, enter the fields above and click Install Integration.

Management API setup

curl -X POST http://localhost:8084/v1/admin/integration-catalog/outreach/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "name": "Outreach",
  "variant": "default",
  "config": {
    "client_id": "your_client_id",
    "client_secret": "your_client_secret",
    "refresh_token": "your_refresh_token"
  },
  "delivery_mode": "server_side"
}'

What Signal sends

An example request, rendered from the default preset for generate_lead:

POST https://api.outreach.io/api/v2/prospects
 
{
  "data": {
    "attributes": {
      "addressCity": "Bath",
      "addressCountry": "GB",
      "addressState": "Somerset",
      "addressZip": "BA1 1AA",
      "campaignName": "autumn_launch",
      "company": "Acme Ltd",
      "emails": [
        "neill@example.com"
      ],
      "externalId": "0f8fad5b-d9cb-469f-a165-70867728950e",
      "firstName": "Neill",
      "lastName": "Mcfixture",
      "mobilePhones": [
        "+447700900123"
      ],
      "source": "google",
      "tags": [
        "Signal",
        "lead"
      ],
      "title": "Head of Growth",
      "websiteUrl1": "https://acme.example"
    },
    "type": "prospect"
  }
}

Presets

Events not listed are not sent. Each preset is a starting point: add, rename or remove mappings on the installed integration.

Notes and limits

• The call creates a prospect. Outreach rejects a second prospect with the same email (422), so a repeat submission from a known prospect is not an update; it is recorded as a permanent failure.
• Outreach has no server-side event ingestion API, so page views and product events are not sent.

Consent

Assign the consent category you use for this processing when you install Outreach, so an event is delivered only when the visitor has granted it. Signal never writes a cookie-banner choice into Outreach’s contact permissions (optedOut, emailOptedOut, callOptedOut): consent to cookies is not consent to be emailed, called or messaged. Record communication opt-in and opt-out in Outreach.

Verify it’s working

1. Open the integration in the Signal Management UI and watch Live Events while you trigger a mapped event.
2. Confirm a 2xx response from Outreach.
3. Find the record in Outreach and check it arrived.

Troubleshooting