Outreach

Outreach is a leading sales engagement platform that helps sales teams streamline their outreach processes, manage prospect interactions, and optimize sales performance through automated sequences, analytics, and CRM integration for improved sales efficiency and results.

Power end-to-end data operations for your Outreach API with Nexla. Our bi-directional Outreach connector is purpose-built for Outreach, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Outreach or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Outreach workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating an Outreach credential, you need to obtain your OAuth2 Client ID and Client Secret from your Outreach account. Outreach uses OAuth2 3-legged authentication, which allows Nexla to access your Outreach account on your behalf.

To prepare for OAuth2 authentication, ensure you have the following:

1. Outreach Account: You must have an active Outreach account with appropriate permissions to register OAuth2 applications.

2. OAuth2 Client Application: You must have an OAuth2 client application registered in your Outreach account. If you don't have one, you'll need to create it in your Outreach account settings or developer portal.

3. Client ID and Client Secret: You need to obtain the Client ID and Client Secret from your OAuth2 client application settings in your Outreach account.

4. Account Access: You must have administrative access or appropriate permissions to register OAuth2 applications and authorize access to your Outreach account.

5. OAuth Authorization: During the credential creation process, you will be redirected to Outreach's authorization page to grant Nexla permission to access your Outreach account. You will need to sign in with your Outreach account and approve the authorization request.

The OAuth2 flow uses your OAuth2 client application to authenticate with Outreach. When you authorize Nexla, you grant permission for Nexla to access your Outreach account data based on the requested scopes (e.g., accounts.all, opportunities.all, prospects.all). The authorization includes access to read and manage data in your Outreach account. For detailed information about OAuth2 authentication, available scopes, and API access, refer to the Outreach API documentation.

Authenticate

Credentials required

Authenticate with Outreach using OAuth2 3-legged authentication. Requires a Client ID, Client Secret, and Scope from your OAuth2 client application.

Field	Required	Secret	Description
Client ID for Authorization	Yes	No	Outreach Client ID
Scope	Yes	No	Outreach API Authorized Scopes
Client ID [Duplicate Entry] for Token	Yes	Yes	OAuth App Client ID for fetching token
Client Secret	Yes	Yes	OAuth App Client Secret for fetching token

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Outreach

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Outreach uses OAuth2 3-legged authentication to securely access your Outreach account. Enter your OAuth2 Client ID in the Client ID for Authorization field. This is the Client ID you obtained from your Outreach OAuth2 client application settings. The Client ID is used in the OAuth2 authorization flow to identify your application.

4. Enter your OAuth2 Client Secret in the Client Secret field. This is the Client Secret you obtained from your Outreach OAuth2 client application settings. The Client Secret is used in the OAuth2 token exchange and is sensitive information that must be kept confidential.

5. Select the OAuth2 scopes in the Scope field. The default scopes include accounts.all, opportunities.all, prospects.all, profiles.all, tasks.all, teams.all, stages.all, users.all, and opportunityStages.all. You can select multiple scopes based on the Outreach API resources you need to access. The scopes determine which Outreach API capabilities Nexla will have access to.

6. Click the Authorize button to begin the OAuth2 authorization process. You will be redirected to Outreach's authorization page.

7. Sign in to your Outreach account using your Outreach account credentials.

8. Review the permissions that Nexla is requesting. These permissions allow Nexla to access your Outreach account data based on the selected scopes.

9. Click Accept or Authorize to grant Nexla permission to access your Outreach account.

10. After authorization, you will be redirected back to Nexla, and the credential will be automatically configured with the OAuth2 tokens.

    OAuth2 authentication uses your OAuth2 client application to securely access your Outreach account. When you authorize Nexla, you grant permission for Nexla to access your Outreach account data based on the requested scopes (e.g., accounts.all, opportunities.all, prospects.all). The authorization includes access to read and manage data in your Outreach account.

    The OAuth2 tokens (access token and refresh token) are automatically managed by Nexla. The access token is used to authenticate API requests, and the refresh token is used to obtain new access tokens when they expire. Tokens are automatically refreshed as needed to maintain access to your Outreach account.

    If you need to revoke access, you can do so in your Outreach account settings under OAuth2 applications or Connected apps. For detailed information about OAuth2 authentication, available scopes, and API access, see the Outreach API documentation.

11. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Outreach connector tile, then select the credential that will be used to connect to your Outreach account, and click Next; or, create a new Outreach credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Outreach endpoints. Each template is designed specifically for the corresponding Outreach endpoint, making data source setup easy and efficient. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

Fetch all Records of a Resource

This endpoint template fetches all records of any Outreach resource type. Use this template when you need to retrieve multiple records from a specific resource type, such as accounts, opportunities, prospects, tasks, or other Outreach resources. Use the advanced tab for fetching a filtered list of records.

• Enter the resource type in the Resource Type field. This should be the type of Outreach resource whose records you wish to fetch (e.g., accounts, opportunities, prospects, tasks, users). The resource type determines which Outreach resource will be queried. Refer to the Outreach API documentation for available resource types.

This endpoint fetches all records of a specific Outreach resource type. The endpoint uses next URL-based pagination to handle large datasets efficiently. Nexla will automatically fetch subsequent pages of data by following the links.next URL returned in the API response. The endpoint returns up to 100 records per page by default.

You can use the advanced tab to fetch a filtered list of records by adding query parameters or filters. For detailed information about resource types, API response structures, pagination, and available resource data, see the Outreach API documentation.

Fetch One Record of a Resource

This endpoint template fetches a specific record of any Outreach resource type by its ID. Use this template when you need to retrieve a single record from a specific resource type, such as a specific account, opportunity, prospect, task, or other Outreach resource. Use the advanced tab for fetching a filtered list of records.

• Enter the resource type in the Resource Type field. This should be the type of Outreach resource whose record you wish to fetch (e.g., accounts, opportunities, prospects, tasks, users). The resource type determines which Outreach resource will be queried.
• Enter the resource ID in the Resource ID field. This should be the unique identifier of the specific record you want to retrieve. The resource ID is used to fetch a single record from the specified resource type.

This endpoint fetches a specific record by its ID from a specific Outreach resource type. The endpoint returns a single record matching the specified resource type and resource ID. You can use the advanced tab to fetch additional related data or apply filters.

For detailed information about resource types, resource IDs, API response structures, and available resource data, see the Outreach API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Outreach data sources can also be manually configured to ingest data from any valid Outreach API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom query parameters and filters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Outreach API endpoints typically use the GET method and follow the pattern https://api.outreach.io/api/v2/<resource> (e.g., https://api.outreach.io/api/v2/accounts, https://api.outreach.io/api/v2/opportunities), including any required query parameters such as ?page[size]=100&count=false. Set the Response Data Path to $.data[*] to extract all records from a collection endpoint, or $ for single-record endpoints. The API uses next URL-based pagination via links.next; when configuring pagination, use $.links["next"] as the JSONPath expression to the next page URL.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Outreach data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.