Zendesk Sell

Zendesk Sell is a sales CRM that helps teams manage leads, contacts, deals, and sales activities in one place. Its REST API is served from api.getbase.com and exposes CRM objects such as leads, contacts, deals, notes, tasks, and pipeline metadata. This connector lets Nexla ingest those objects as a data source and create records in Zendesk Sell as a destination.

Power end-to-end data operations for your Zendesk Sell API with Nexla. Our bi-directional Zendesk Sell connector is purpose-built for Zendesk Sell, 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 Zendesk Sell or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Zendesk Sell 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 a Zendesk Sell credential, you need a Zendesk Sell OAuth access token. The Zendesk Sell API uses bearer-token authentication: the token is sent in the Authorization header as Bearer <token> on every request to the API base URL https://api.getbase.com/v2/. A Sell personal access token is long-lived and is well suited to server-to-server integrations where you access your own Zendesk Sell data.

To create a Zendesk Sell access token, follow these steps:

1. Sign in to Zendesk Sell with an administrator account.

2. Click Settings in the Sell sidebar.

3. Navigate to Integrations > OAuth > Access Tokens.

4. Click + Add Access Token, enter a description that identifies this token (for example, "Nexla Integration"), and click Save.

5. Copy the generated access token and store it securely. Treat it as a secret, since it grants API access to your Zendesk Sell data.

The Sell OAuth access token is not the same as the OAuth token created in the Zendesk Admin Center. You can create multiple personal access tokens, and each one can be revoked and recreated independently. For more detail, see the Zendesk help article on creating a Sell OAuth access token and the Zendesk Sell API reference.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key	Yes	Yes	API key.

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.

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

3. Enter your Zendesk Sell OAuth access token in the API Key field. Nexla sends this token in the Authorization header as a bearer token on every request to the Zendesk Sell API.

   If your access token is compromised, revoke it in your Zendesk Sell settings under Settings > Integrations > OAuth > Access Tokens and create a new one. The access token grants access to your Zendesk Sell data and should be kept confidential.

   For detailed information about authentication and available resources, see the Zendesk Sell API reference.

4. 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.

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 Zendesk Sell connector tile, then select the credential that will be used to connect to Zendesk Sell, and click Next; or, create a new Zendesk Sell 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 Zendesk Sell endpoints. 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.

List Users

This endpoint template retrieves users from your Zendesk Sell account.

• Data is fetched from the /v2/users endpoint. This endpoint is paginated, and Nexla automatically advances through the pages to retrieve the full result set.

For detailed information about the response structure and available fields, see the Zendesk Sell API reference.

List Orders

This endpoint template retrieves orders from your Zendesk Sell account.

• Data is fetched from the /v2/orders endpoint. This endpoint is paginated, and Nexla automatically advances through the pages to retrieve the full result set.

For detailed information about the response structure and available fields, see the Zendesk Sell API reference.

List Contacts

This endpoint template retrieves contacts from your Zendesk Sell account.

• Data is fetched from the /v2/contacts endpoint. This endpoint is paginated, and Nexla automatically advances through the pages to retrieve the full result set.

For detailed information about the response structure and available fields, see the Zendesk Sell API reference.

List Call Outcomes

This endpoint template retrieves call outcomes from your Zendesk Sell account.

• Data is fetched from the /v2/call_outcomes endpoint. This endpoint is paginated, and Nexla automatically advances through the pages to retrieve the full result set.

For detailed information about the response structure and available fields, see the Zendesk Sell API reference.

List Calls

This endpoint template retrieves calls from your Zendesk Sell account.

• Data is fetched from the /v2/calls endpoint. This endpoint is paginated, and Nexla automatically advances through the pages to retrieve the full result set.

For detailed information about the response structure and available fields, see the Zendesk Sell API reference.

List Collaborations

This endpoint template retrieves collaborations from your Zendesk Sell account.

• Data is fetched from the /v2/collaborations endpoint. This endpoint is paginated, and Nexla automatically advances through the pages to retrieve the full result set.

For detailed information about the response structure and available fields, see the Zendesk Sell API reference.

List Leads

This endpoint template retrieves leads from your Zendesk Sell account.

• Data is fetched from the /v2/leads endpoint. This endpoint is paginated, and Nexla automatically advances through the pages to retrieve the full result set.

For detailed information about the response structure and available fields, see the Zendesk Sell API reference.

List Lead Conversions

This endpoint template retrieves lead conversions from your Zendesk Sell account.

• Data is fetched from the /v2/lead_conversions endpoint. This endpoint is paginated, and Nexla automatically advances through the pages to retrieve the full result set.

For detailed information about the response structure and available fields, see the Zendesk Sell API reference.

List Lead Sources

This endpoint template retrieves lead sources from your Zendesk Sell account.

• Data is fetched from the /v2/lead_sources endpoint. This endpoint is paginated, and Nexla automatically advances through the pages to retrieve the full result set.

For detailed information about the response structure and available fields, see the Zendesk Sell API reference.

List Lead Unqualified Reasons

This endpoint template retrieves lead unqualified reasons from your Zendesk Sell account.

• Data is fetched from the /v2/lead_unqualified_reasons endpoint. This endpoint is paginated, and Nexla automatically advances through the pages to retrieve the full result set.

For detailed information about the response structure and available fields, see the Zendesk Sell API reference.

List Deal Sources

This endpoint template retrieves deal sources from your Zendesk Sell account.

• Data is fetched from the /v2/deal_sources endpoint. This endpoint is paginated, and Nexla automatically advances through the pages to retrieve the full result set.

For detailed information about the response structure and available fields, see the Zendesk Sell API reference.

List Deal Unqualified Reasons

This endpoint template retrieves deal unqualified reasons from your Zendesk Sell account.

• Data is fetched from the /v2/deal_unqualified_reasons endpoint. This endpoint is paginated, and Nexla automatically advances through the pages to retrieve the full result set.

For detailed information about the response structure and available fields, see the Zendesk Sell API reference.

List Deals

This endpoint template retrieves deals from your Zendesk Sell account.

• Data is fetched from the /v2/deals endpoint. This endpoint is paginated, and Nexla automatically advances through the pages to retrieve the full result set.

For detailed information about the response structure and available fields, see the Zendesk Sell API reference.

List Loss Reasons

This endpoint template retrieves loss reasons from your Zendesk Sell account.

• Data is fetched from the /v2/loss_reasons endpoint. This endpoint is paginated, and Nexla automatically advances through the pages to retrieve the full result set.

For detailed information about the response structure and available fields, see the Zendesk Sell API reference.

List Notes

This endpoint template retrieves notes from your Zendesk Sell account.

• Data is fetched from the /v2/notes endpoint. This endpoint is paginated, and Nexla automatically advances through the pages to retrieve the full result set.

For detailed information about the response structure and available fields, see the Zendesk Sell API reference.

List Pipelines

This endpoint template retrieves pipelines from your Zendesk Sell account.

• Data is fetched from the /v2/pipelines endpoint. This endpoint is paginated, and Nexla automatically advances through the pages to retrieve the full result set.

For detailed information about the response structure and available fields, see the Zendesk Sell API reference.

List Products

This endpoint template retrieves products from your Zendesk Sell account.

• Data is fetched from the /v2/products endpoint. This endpoint is paginated, and Nexla automatically advances through the pages to retrieve the full result set.

For detailed information about the response structure and available fields, see the Zendesk Sell API reference.

List Stages

This endpoint template retrieves stages from your Zendesk Sell account.

• Data is fetched from the /v2/stages endpoint. This endpoint is paginated, and Nexla automatically advances through the pages to retrieve the full result set.

For detailed information about the response structure and available fields, see the Zendesk Sell API reference.

List Tags

This endpoint template retrieves tags from your Zendesk Sell account.

• Data is fetched from the /v2/tags endpoint. This endpoint is paginated, and Nexla automatically advances through the pages to retrieve the full result set.

For detailed information about the response structure and available fields, see the Zendesk Sell API reference.

List Tasks

This endpoint template retrieves tasks from your Zendesk Sell account.

• Data is fetched from the /v2/tasks endpoint. This endpoint is paginated, and Nexla automatically advances through the pages to retrieve the full result set.

For detailed information about the response structure and available fields, see the Zendesk Sell API reference.

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

Zendesk Sell data sources can also be manually configured to ingest data from any valid Zendesk Sell API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. 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.

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 Zendesk Sell 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.

Use as a destination

Click the + icon on the Nexset that will be sent to the Zendesk Sell destination, and select the Send to Destination option from the menu. Select the Zendesk Sell connector from the list of available destination connectors, then select the credential that will be used to connect to Zendesk Sell, and click Next; or, create a new Zendesk Sell credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Zendesk Sell endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Create Contact

Create a new contact (person or organization) in Zendesk Sell.

• Records from the Nexset are sent as JSON in the request body to the /v2/contacts endpoint. Each record is sent as a separate request to create one contact, and the record must match the field structure expected by the Zendesk Sell API.

For detailed information about request body formats and available fields, see the Zendesk Sell contacts reference.

Create Lead

Create a new lead (person or organization) in Zendesk Sell.

• Records from the Nexset are sent as JSON in the request body to the /v2/leads endpoint. Each record is sent as a separate request to create one lead, and the record must match the field structure expected by the Zendesk Sell API.

For detailed information about request body formats and available fields, see the Zendesk Sell leads reference.

Create Deal

Create a new deal in Zendesk Sell.

• Records from the Nexset are sent as JSON in the request body to the /v2/deals endpoint. Each record is sent as a separate request to create one deal, and the record must match the field structure expected by the Zendesk Sell API.

For detailed information about request body formats and available fields, see the Zendesk Sell deals reference.

Create Note

Create a new note and associate it with a lead, contact, or deal in Zendesk Sell.

• Records from the Nexset are sent as JSON in the request body to the /v2/notes endpoint. Each record is sent as a separate request to create one note, and the record must reference the resource it is attached to and match the field structure expected by the Zendesk Sell API.

For detailed information about request body formats and available fields, see the Zendesk Sell notes reference.

Create Task

Create a new task in Zendesk Sell.

• Records from the Nexset are sent as JSON in the request body to the /v2/tasks endpoint. Each record is sent as a separate request to create one task, and the record must match the field structure expected by the Zendesk Sell API.

For detailed information about request body formats and available fields, see the Zendesk Sell tasks reference.

Manual configuration

Zendesk Sell destinations can also be manually configured to send data to any valid Zendesk Sell API endpoint. 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, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Zendesk Sell endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Zendesk Sell endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.