Zendesk Feeds

Zendesk is a customer service and engagement platform that helps businesses manage support tickets, users, organizations, and teams. The Zendesk Feeds connector is a source-only ELT connector that ingests Zendesk data as a set of feeds. Select from tickets, users, organizations, and groups, and Nexla full-refreshes each selected feed on a schedule using API token authentication.

Power end-to-end data operations for your Zendesk Feeds API with Nexla. Our bi-directional Zendesk Feeds connector is purpose-built for Zendesk Feeds, 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 Feeds or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Zendesk Feeds 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

The Zendesk Feeds connector authenticates with a Zendesk API token, combined with your account email address and Zendesk subdomain. Before creating a credential in Nexla, gather the following from your Zendesk account.

Your Zendesk subdomain

Your subdomain is the first part of your Zendesk URL. For example, if you access Zendesk at https://yourcompany.zendesk.com, then your subdomain is yourcompany. You will enter the subdomain (not the full URL) when configuring the Nexla credential.

Enable API token access and create a token

API token access must be enabled by an administrator, and API tokens are created in the Zendesk Admin Center.

1. Sign in to Zendesk with an account that has administrator permissions.

2. In Admin Center, click Apps and integrations in the sidebar, then select APIs > Zendesk API.

3. On the Settings tab, enable Token access if it is not already turned on.

4. Open the API tokens tab and click Add API token.

5. Optionally enter a description (for example, Nexla Integration) to identify the token's purpose.

6. Click Save to generate the token. Copy the token immediately and store it somewhere secure.

   Important

   The full API token is displayed only once. After you close the dialog, Zendesk will not show the token value again. If you lose it, revoke the token and generate a new one.

Build the Base64-encoded authentication string

Zendesk API token authentication uses the string {email_address}/token:{api_token}, Base64-encoded and sent in the Authorization header. Construct the value in three steps:

1. Combine your account email, the literal /token: separator, and your API token — for example, agent@yourcompany.com/token:abc123DEF456.

2. Base64-encode that entire string.

3. Use the resulting Base64 value when creating the Nexla credential.

Zendesk is deprecating API tokens as an authentication method. Confirm your account's current API access options in the Zendesk Admin Center before relying on API token authentication for long-lived integrations. For details, see the Zendesk API token access documentation and Zendesk security and authentication reference.

Authenticate

Credentials required

Field	Required	Secret	Description
Zendesk Subdomain	Yes	No	Your Zendesk subdomain (e.g., yourcompany in https://yourcompany.zendesk.com)
Base64 Encoded Email/token:API_Token	Yes	Yes	Base64 encode your 'email/token:api_token' value.

Create a credential in Nexla

1. After selecting the data source 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.

   Resource descriptions are recommended but are not required. Use them to identify the Zendesk account or subdomain represented by this credential.

3. Enter your Zendesk subdomain in the Zendesk Subdomain field. This is the first part of your Zendesk URL (for example, yourcompany for https://yourcompany.zendesk.com) and is used to construct the API request URL.

4. Enter the Base64-encoded authentication string you built in Prerequisites in the Base64 Encoded Email/token:API_Token field. Nexla sends this value in the Authorization header as Basic <encoded value> when ingesting feeds. This value is treated as a secret and is stored securely by Nexla.

5. 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 creation and can be selected for use with Zendesk Feeds flows.

Use as a data source

How This Connector Works

The Zendesk Feeds connector is a source-only ELT connector. Rather than configuring one endpoint at a time, you select the Zendesk objects you want to ingest, and Nexla reads each selected object as its own feed.

• Object selection: When you create the source, Nexla presents the available Zendesk objects (tickets, users, organizations, and groups) for selection.

• Full refresh: Each selected feed is ingested using a full-refresh strategy, so every run reads the complete current set of records for that object. The id field is used as the primary key to uniquely identify records within each feed.

• Automatic pagination: Zendesk list endpoints return results across multiple pages. Nexla follows the Zendesk next_page links automatically while reading each feed, so a full refresh ingests all available pages for the selected objects.

Create a New Data Flow

1. To create a new data flow, navigate to the Integrate section, click the New Data Flow button, select the ELT flow type, and click Create.

2. Select the Zendesk Feeds connector tile from the list of available connectors. Then, select the credential that will be used to connect to your Zendesk account and click Next; or, create a new Zendesk Feeds credential for use in this flow.

Select the Objects to Ingest

After authenticating, Nexla lists the Zendesk objects available from the connector. Select one or more of the following objects to ingest. Each selected object becomes its own feed and is full-refreshed on the configured schedule.

Tickets

Retrieves tickets from your Zendesk account. Tickets are the core support records in Zendesk, tracking customer requests and the conversations, status, and assignments associated with them.

• Select Tickets from the list of available objects.
• The feed reads from the Zendesk tickets.json endpoint and ingests all records under the response tickets array, using id as the primary key.

Users

Retrieves users from your Zendesk account. Users include end users (customers), agents, and administrators, along with their profile and contact details.

• Select Users from the list of available objects.
• The feed reads from the Zendesk users.json endpoint and ingests all records under the response users array, using id as the primary key.

Organizations

Retrieves organizations from your Zendesk account. Organizations group related users together, and are often used to represent the companies or accounts your end users belong to.

• Select Organizations from the list of available objects.
• The feed reads from the Zendesk organizations.json endpoint and ingests all records under the response organizations array, using id as the primary key.

Groups

Retrieves groups from your Zendesk account. Groups organize agents into teams that tickets can be assigned to, reflecting how support work is routed within your organization.

• Select Groups from the list of available objects.
• The feed reads from the Zendesk groups.json endpoint and ingests all records under the response groups array, using id as the primary key.

For object schemas, field definitions, and additional detail on each Zendesk endpoint, see the Zendesk API reference.

Schedule and Activate

• Set or adjust the polling schedule in the source settings before activating the flow. The default schedule runs once per day; on each run, every selected feed is full-refreshed.

• Once the source is configured, activate the flow to begin ingesting data. Nexla will organize the data that it finds into one or more Nexsets.