Reference · built on requestConnectorCRM & sales

Outreach

Prospects, accounts, sequences, mailings, calls, and tasks from Outreach through its JSON:API interface and webhooks.

Request accessPricing ↗

About

Outreach is a sales execution platform. Its REST interface at https://api.outreach.io/api/v2 follows the JSON:API 1.0 specification, so every request carries Content-Type application/vnd.api+json and collections take filters, sorts, sparse fieldsets, includes, and cursor paging. Webhooks post created, updated, and destroyed events for prospects, accounts, sequences, sequence states, mailings, calls, tasks, and opportunities, with mailing-level events such as delivered, opened, and replied.

An operator on Fibric reads sequence states and mailing outcomes and proposes a sequence enrollment, a task, or a call log. You approve it in Outreach's terms; the write happens once, and a receipt keeps what changed, why, and how to reverse it.

This is a reference listing. It documents what Fibric would read from Outreach and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Prospects and accounts, filtered with filter[field]=value, comma lists, ranges such as 5..10, and __null__
  • Sequences, sequenceSteps, and sequenceStates in states active, pending, finished, paused, disabled, failed, bounced, or opted_out
  • Mailings, calls, tasks with action and state filters, opportunities, and users
  • Events through GET /api/v2/events sorted by updatedAt
  • Webhook deliveries for created, updated, and destroyed on prospect, account, sequence, sequenceState, mailing, call, task, opportunity, and user, plus bounced, delivered, opened, replied, and completed

Proposed actions

  • Target capability: propose enrolling a prospect through POST /api/v2/sequenceStates with prospect, sequence, and mailbox relationships
  • Target capability: propose pausing, resuming, or finishing a sequence state through its actions endpoint
  • Target capability: propose creating a prospect or account, or a PATCH that touches only the fields that changed
  • Target capability: propose a task, or a call record with direction and outcome, linked to a prospect and a user

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Enroll a new lead in the right sequence

    Match an inbound lead to a prospect by email, read the account's owner and stage, and propose a sequenceState with the owner's mailbox for approval.

    With Lead Response

  • Retire sequences that finished without a reply

    Read sequenceStates in the finished state with no replied mailing, and propose a task for the owner or a move to a different sequence.

    With Stale Pipeline

  • Notice a customer going quiet

    Combine opted_out and bounced states with the account's recent events, and propose a churn review task for the account owner.

    With Churn Watch

Requirements

  • An Outreach app with redirect URIs and OAuth data scopes set on its API access tab
  • A user in your Outreach org who completes the authorization flow; requests run as that user
  • Content-Type: application/vnd.api+json on every request, or Outreach answers 415
  • An HTTPS URL for webhooks and a secret if you want the Outreach-Webhook-Signature header to check
Authentication
OAuth 2.0 from an app registered in the Outreach developer portal: authorize at https://api.outreach.io/oauth/authorize, exchange the code at https://api.outreach.io/oauth/token, and refresh access tokens that expire after 7200 seconds.

Limits

  • 10,000 requests per hour per user for general endpoints, reported in X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset
  • Kaia recordings and transcripts are capped at 3 API calls per second and 6,000 per day per organization
  • Webhook deliveries time out after 5 seconds and get 4 attempts, retried only on network failure, never on an HTTP error code
  • Cursor paging returns up to 50 records per page; offset paging is deprecated and stops at offset 10,000

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Outreach ↗

Questions and answers

How does Outreach paginate large collections?
With cursors: page[size] up to 50 plus page[after] or page[before], ideally with count=false. Offset paging using page[offset] and page[limit] still works but is deprecated and stops at offset 10,000.
Does Outreach retry a failed webhook?
Only on network failure. Outreach waits 5 seconds for a response, makes 4 attempts with 1-second pauses, does not follow redirects, and does not retry when your endpoint returns an HTTP error code such as 500 or 429.
What does the access token lifecycle look like?
Your app sends the user to https://api.outreach.io/oauth/authorize with a state parameter, exchanges the code at https://api.outreach.io/oauth/token, and receives an access token that expires in 7200 seconds plus a refresh token used with grant_type refresh_token.
Ask about Outreach

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Outreach through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy