Advanced Analytica Advanced Analytica: IBOM
← All connectors
Zendesk Support logo

Source connector

Zendesk Support

Set up Zendesk Support as a source and move its data into your chosen destination.

Version 5.7.0 certified generally available

Zendesk Support

Use this page to set up the Zendesk Support source connector and find reference information.

Prerequisites

  • A Zendesk account. An Administrator role gives you full access to every stream. Non-admin accounts can still sync. Streams requiring admin permissions are skipped automatically.
  • The account’s unique Zendesk subdomain.

Setup guide

Set up Zendesk Support

You can authenticate the Zendesk Support source connector in three ways:

  • OAuth 2.0 with refresh token (recommended)
  • API token (Zendesk disables new API token creation on October 27, 2026, as explained in the following caution)
  • OAuth 2.0 Legacy (for existing OAuth connections that haven’t migrated to the refresh token flow)

:::note Zendesk requires the refresh token flow for all customers as of April 30, 2026. Legacy OAuth access tokens don’t expire or support refreshing. Migrate existing connections to OAuth 2.0 with Refresh Token. :::

:::caution Zendesk is removing API tokens as an authentication method. From October 27, 2026, Zendesk accounts can’t create new API tokens. You can only use API Token authentication with an existing active token. Zendesk also deactivates tokens that remain unused for 30 days. On April 30, 2027, Zendesk permanently deactivates every remaining API token. Sources using these tokens then stop syncing. Set up new sources with OAuth 2.0 with Refresh Token. Switch existing API token sources to OAuth before April 30, 2027. :::

For Airbyte Cloud:

OAuth is strongly recommended for authenticating your Zendesk Support account. It simplifies setup and lets you authenticate directly from the Airbyte UI.

For Airbyte Open Source:

OAuth is recommended for authenticating your Zendesk Support account. See Generate OAuth credentials.

Generate an API token

:::note Zendesk disables API token creation on October 27, 2026. After this date, you can’t create a token using these steps. Existing tokens continue working until Zendesk deactivates all API tokens on April 30, 2027. If you can’t create a token, generate OAuth credentials instead. :::

  1. Log in to your Zendesk account.

  2. Click the Zendesk Products icon (four squares) in the top-right corner, then select Admin Center.

  3. In the left navbar, click Apps and Integrations, then select APIs > Zendesk API.

  4. In the Settings tab, toggle the option to enable token access.

  5. Click the Add API token button. You can optionally provide a token description.

    :::caution Copy the token and store it securely. You can’t access its value after closing the page. :::

  6. Click Save.

Generate OAuth credentials

Airbyte Cloud runs the OAuth flow for you. With self-managed Airbyte, create the credentials and enter a client ID, client secret and refresh token.

  1. Register an OAuth client in Admin Center. See Registering your application with Zendesk. Note the client’s unique identifier and secret.
  2. Complete Zendesk’s authorization code flow with the read scope. Include expires_in in the token request. Zendesk only issues a refresh token when the access token expires. Clients created before April 30, 2026 have no default expiration. Therefore, a request without expires_in returns a token you can’t refresh. The maximum value is 172800 (48 hours). The connector requests this value in Airbyte Cloud.
  3. Save the refresh_token from the response.

When configuring the source, select OAuth2.0 with Refresh Token and enter the client ID, client secret and refresh token. Leave Access Token and Token Expiry Date empty. On its first request, the connector exchanges the refresh token for an access token. It then writes the new access token, refresh token and expiry to the source configuration.

:::caution Zendesk refresh tokens are single-use. Each refresh returns a new refresh token and invalidates the previous token. A refresh token can therefore support only one source. Don’t copy the same value into another source or Airbyte deployment. :::

Set up the connector in Airbyte

Airbyte Cloud

  1. Log into your Airbyte Cloud account.
  2. Click Sources and then click + New source.
  3. On the Set up the source page, select Zendesk Support from the Source type dropdown.
  4. Enter a name for the Zendesk Support connector.

Airbyte Open Source

  1. Go to the Airbyte Open Source dashboard.
  2. Click Sources and then click + New source.
  3. On the Set up the source page, select Zendesk Support from the Source type dropdown.
  4. Enter a name for the Zendesk Support connector.
  1. Authenticate your Zendesk Support account using OAuth or an API token.
  • For Airbyte Cloud: To use OAuth, select OAuth 2.0 with Refresh Token from the Authentication dropdown. Then click Authenticate your Zendesk Support account to sign in with Zendesk Support and authorise your account.
  • For Airbyte Open Source: To use OAuth, select OAuth2.0 with Refresh Token from the Authentication dropdown. Enter the client ID, client secret and refresh token you generated. To use an existing API token, select API Token. Enter the token and the email address linked to your Zendesk Support account. API tokens stop working on April 30, 2027.
  1. For Subdomain, enter your Zendesk subdomain from your account URL. For example, if your account URL is https://MY_SUBDOMAIN.zendesk.com/, your subdomain is MY_SUBDOMAIN.
  2. (Optional) For Start Date, use the datepicker. Alternatively, enter a UTC date and time programmatically using the format YYYY-MM-DDTHH:mm:ssZ. Data added on or after this date will be replicated. If you leave this field blank, Airbyte replicates the last two years of data by default.
  3. (Optional) For Number of concurrent threads, enter the number of parallel threads used for the sync. The default is 4, and the minimum is 2. Increase this value if your Zendesk plan supports higher rate limits. See Rate limiting for details.
  4. (Optional) For Page Size (ticket_comments), enter the number of records per page for the ticket_comments stream. The default is 100, and the maximum is 1000. Lower values can help prevent timeouts on large Zendesk instances.
  5. (Optional) For Tickets Search Lookback Window (days), enter how many days the tickets_search stream re-scans during each sync. The default is 0. This setting affects only the opt-in tickets_search stream. See Tickets stream: change tracking.
  6. Click Set up source and wait for the tests to finish.

Supported sync modes

The Zendesk Support source connector supports these sync modes:

  • Full Refresh | Overwrite
  • Full Refresh | Append
  • Incremental Sync | Append
  • Incremental Sync | Deduped History

:::note Two types of incremental sync are available:

  1. Incremental (standard server-side, where the API returns only data updated or created since the previous sync).
  2. Client-Side Incremental (the API returns all available data, and the connector keeps only new records). :::

Supported streams

The Zendesk Support source connector supports these streams:

Deleted records

The Zendesk Support connector fetches deleted records from these streams:

StreamDeletion indicator field
Brandsis_deleted
Deleted TicketsAll records are deleted
Groupsdeleted
Organizationsdeleted_at
Ticket Metric Eventsdeleted

:::note In versions 5.2.0 to 5.4.x, the tickets stream didn’t include deleted tickets. From version 5.5.0, the tickets stream again includes deleted tickets, as explained below. The deleted_tickets stream remains available. Pair it with the opt-in tickets_search stream, which doesn’t return deleted tickets. :::

Track ticket changes

The tickets stream uses Zendesk’s Incremental Ticket Export endpoint, which tracks changes by generated_timestamp. Zendesk updates generated_timestamp after every ticket change. This includes updates driven by automations, macros and systems, such as auto-solve batches. The stream therefore reliably re-syncs every update.

:::warning Versions 5.2.0 to 5.4.x used the Export Search Results endpoint and tracked changes by updated_at. Zendesk updates updated_at and re-indexes a ticket for search only when a change generates a ticket event. Therefore, incremental syncs silently missed updates driven by automations, macros and systems. and also returned stale field values, such as status, during historical reads. This happened because search/export is served from Zendesk’s search index rather than the live record. Version 5.5.0 fixed this issue by reverting the tickets stream to generated_timestamp. After upgrading, a one-time state migration automatically backfills records missed or left stale since 2026-03-01. You don’t need to reset anything manually. See the migration guide. :::

The tickets_search stream preserves the former Export Search Results behaviour. It provides higher throughput: 100 req/min, compared with 10 req/min for the incremental endpoint. Its 30-day time-range partitions also sync concurrently, and it offers a configurable Tickets Search Lookback Window (days) setting. However, it shares the limitations in versions 5.2.0 to 5.4.x. In incremental mode, it can miss updates driven by automations, macros and systems. It can also return stale statuses during historical reads. Use tickets_search only when throughput matters more than completeness. Pair it with the deleted_tickets stream because Export Search excludes deleted tickets.

tickets_search isn’t enabled by default. Enable it on your connection’s Schema tab. Enabling both tickets and tickets_search syncs the same tickets twice. Most people should enable only one.

Audits for archived tickets

Zendesk automatically archives tickets around 120 days after they close. The ticket_audits stream reads the List All Ticket Audits endpoint. Zendesk documents this endpoint as excluding archived tickets. Therefore, ticket_audits returns no audits for archived tickets. This includes audits added after archiving, such as those created by a bulk update.

The ticket_audits_per_ticket stream reads List Audits for a Ticket for each ticket returned by the tickets stream’s incremental export. This endpoint includes archived tickets. Its records contain the same fields as ticket_audits. They also include an _ab_updated_at cursor containing the parent ticket’s generated_timestamp.

ticket_audits_per_ticket isn’t selected by default. Select it on your connection’s Schema tab. First, consider its cost:

  • Each sync makes one request per ticket created or updated since the previous sync. It makes another request for every 100 audits on each ticket. A bulk update affecting 100,000 tickets creates 100,000 requests during the next sync.
  • The first sync reads every ticket updated since Start Date, or during the last two years if blank. It makes one request per ticket. To recover archived-ticket audits changed since a specific date, set Start Date to that date before selecting the stream.
  • These requests count towards your Zendesk plan’s account-wide rate limit. The connector’s other streams and your Zendesk integrations share this limit. The connector doesn’t throttle this stream below the limit. It sends requests as quickly as Number of concurrent threads allows. When Zendesk returns 429 (Too Many Requests), it waits for the period specified in the Retry-After header before retrying. With a 200 requests-per-minute plan, 100,000 tickets take at least eight hours. Other account integrations can be rate limited during the sync.
  • The stream reads its parent tickets through a separate pass over the incremental ticket export. This export shares the 10 requests-per-minute limit with the tickets stream.
  • When a ticket changes, the stream emits all its audits again. Use Incremental | Append + Deduped to keep one row per audit id.

:::warning If your connection’s schema change setting is Propagate all field and stream changes, upgrading to version 5.7.0 automatically starts syncing ticket_audits_per_ticket. The costs described above apply. If you don’t need archived-ticket audits, deselect ticket_audits_per_ticket on the connection’s Schema tab. :::

ticket_audits remains unchanged. You can continue using it, switch to ticket_audits_per_ticket or sync both. Both streams share audit id values, so you can combine them downstream.

Limitations and troubleshooting

Expand to see details about Zendesk Support connector limitations and troubleshooting.

Connector limitations

Rate limits

Zendesk applies rate limits according to your plan tier:

PlanRequests per minute
Team200
Growth / Professional400
Enterprise700
Enterprise Plus / High Volume API add-on2500

The connector’s Number of concurrent threads setting controls how many streams sync in parallel. The default is 4. Increase this value for faster syncs if your plan supports higher rate limits. The minimum is 2, and the maximum is 40. With one thread, no other stream emits while the tickets stream reads. From the first sync after upgrading to 5.6.0, a saved value of 1 is treated as 2. The stored configuration is also updated to 2. If the source settings form flags the field before that sync, set it to 2 or more.

Zendesk’s incremental export endpoints have a stricter limit of 10 requests per minute, regardless of plan tier. This limit covers the tickets, ticket_comments, ticket_events, ticket_metric_events, users and organizations streams using incremental exports. The opt-in tickets_search stream uses the Export Search Results endpoint. This endpoint has a separate limit of 100 requests per minute. The deleted_tickets stream has a limit of 10 requests per minute. A built-in API budget automatically throttles requests within these limits. The opt-in ticket_audits_per_ticket stream makes one request per ticket against your plan’s account-wide limit. Your other Zendesk integrations share this limit, and the API budget doesn’t throttle the stream. See Ticket audits for archived tickets.

When the connector receives a 429 (Too Many Requests) response, it follows the Retry-After header and waits before retrying. The ticket_comments stream also retries 504 (Gateway Timeout) errors using exponential backoff. These errors can occur on large Zendesk instances.

The connector shouldn’t encounter Zendesk API limits during normal use. Create an issue if you experience rate-limit issues that aren’t retried successfully.

Permissions and skipped streams

Some streams require administrator-level Zendesk permissions. Examples include account_attributes, attribute_definitions, audit_logs and ticket_forms. If the authenticated user can’t access a stream’s endpoint, the connector skips that stream. It continues syncing the remaining streams. The logs identify skipped streams and explain the permission issue.

To sync every available stream, authenticate with a Zendesk account that has an Administrator role.

Side conversation access

Side conversations are included with Zendesk Suite Professional and above. They’re available to Support Professional and above through the Collaboration add-on. You must also activate side conversations in Admin Center. On Enterprise plans, a custom role can restrict which agents can use them.

Zendesk grants side conversation access per ticket. This stream can read some tickets but be denied access to others. From version 5.5.2, the connector logs a message and skips the affected ticket. It continues syncing the remaining stream when Zendesk returns:

  • 403, when Zendesk denies access to the ticket’s side conversations.
  • 404, when the ticket no longer exists. This is expected because the tickets stream returns deleted tickets.
  • 422, when the ticket type doesn’t support side conversations.

If your account has no side conversations, Zendesk denies every ticket this way. The stream finishes empty instead of failing.

Versions before 5.5.2 failed the entire sync after a 403 or 404. The 422 case has been skipped since 5.4.1. Because side_conversations reads parent tickets incrementally, this failure also stopped the parent cursor from advancing. Each following sync then restarted from the same ticket and failed again. Upgrade to version 5.5.2 or later if your syncs fail this way.

The opt-in tickets_search stream reads Zendesk’s search index. New or updated tickets can take several minutes to appear. Tickets indexed after the sync cursor passes their updated_at value aren’t collected during the next sync. Set Tickets Search Lookback Window (days) to at least 1 to re-scan a trailing window during every sync. The lookback window can’t recover updates driven by automations, macros or systems. These updates never change updated_at. The default tickets stream isn’t affected because it reads the live ticket record instead of the search index.

Troubleshooting

OAuth fails with invalid_grant

Zendesk invalidates each refresh token immediately after use. Authentication fails with invalid_grant when the connector holds a token Zendesk has already rotated. Common causes include:

  • The same refresh token is configured in multiple sources or Airbyte deployments. Generate separate OAuth credentials for each source.
  • The source was configured manually using an already-used refresh token.
  • The source was set up with a connector version earlier than 5.5.1. Those versions didn’t record the access token’s expiry when you authorised the source. The connector therefore treated the token as expired and refreshed it during the initial connection test. This consumed the refresh token saved in the configuration.

To recover, upgrade to version 5.5.1 or later. Then re-authenticate the Airbyte Cloud source or replace the refresh token on self-managed Airbyte.

  • Find common Zendesk Support source connector issues on the Airbyte Forum.

IP allow list

If you use Airbyte Cloud and restrict access to specific IPs, add the Airbyte Cloud IP addresses to your allow list.

Changelog

Expand to review
VersionDatePull RequestSubject
5.7.02026-10-2089571Add the ticket_audits_per_ticket stream, which reads audits ticket by ticket so archived tickets are included. It makes one request per created or updated ticket and isn’t selected by default; connections that propagate new streams automatically start syncing it. ticket_audits is unchanged
5.6.32026-10-1387513Refresh the OAuth access token and retry when Zendesk rejects it with 401 invalid_token, so OAuth connections no longer intermittently fail on ticket_metrics and other streams during token rotation
5.6.22026-10-1388867Update dependencies
5.6.12026-10-0684185Update dependencies
5.6.02026-09-1085760Raise the minimum Number of concurrent threads to 2 and migrate existing single-thread configurations, which hit the heartbeat timeout during long tickets reads
5.5.22026-08-2684353Skip individual tickets that Zendesk refuses on the side_conversations stream instead of failing the whole sync. Access to side conversations is granted per ticket, and the refusal arrives as a 403 with an empty body that the previous filter could not match
5.5.12026-08-1182679Request an explicit 48h access-token lifetime and persist OAuth token expiry on initial authentication, so the first check no longer prematurely refreshes and rotates the single-use refresh token
5.5.02026-08-1083812Promoted release candidate to GA
5.5.0-rc.12026-08-0381640Revert tickets stream to the Incremental Ticket Export endpoint (cursor back to generated_timestamp) to fix silent data loss on system-driven updates introduced in 5.2.0; add the opt-in tickets_search stream. See the migration guide.
5.4.62026-07-2883194Update to CDK 7.23.8 (fixes AirbyteCustomCodeNotPermittedError for bundled custom components) and remove the temporary Cloud version override
5.4.52026-07-281082Roll Cloud back to 5.4.3 — 5.4.4 is built on SDM 7.23.7, which breaks bundled custom components
5.4.42026-07-2883159Update dependencies
5.4.32026-07-2182661Update dependencies
5.4.22026-07-1482080Update dependencies
5.4.12026-07-0681210Fixed side_conversations stream: added millisecond-precision timestamp parsing for cursor field and added error handler to skip tickets returning HTTP 422
5.4.02026-07-0281403Added ticket_events stream for Zendesk Incremental Ticket Event Export API
5.3.12026-06-3081305Update dependencies
5.3.02026-06-2779640Added side_conversations stream to retrieve Side Conversations from tickets
5.2.122026-06-2380725Update dependencies
5.2.112026-06-1680108Update dependencies
5.2.102026-06-1279668Gracefully skip streams when Zendesk returns permission-denied error instead of failing the entire sync
5.2.92026-06-0979583Update dependencies
5.2.82026-06-0277507Update dependencies
5.2.72026-05-1578120Promoted release candidate to GA
5.2.7-rc.42026-05-0777857Step default concurrency back from 5 to 4 while keeping the endpoint-specific HTTP API budget LIVE (incremental 10/min, search/export 100/min, deleted_tickets 10/min)
5.2.7-rc.32026-05-0577784Restore the endpoint-specific HTTP API budget from 5.2.6 (incremental 10/min, search/export 100/min, deleted_tickets 10/min) and remove the subscription_tier config field; keep default concurrency at 5
5.2.7-rc.22026-04-2877548Activate the tier-aware HTTP API budget driven by subscription_tier and raise default concurrency from 4 to 5
5.2.7-rc.12026-04-2376953Add subscription_tier config field, comment out the existing HTTP API budget for concurrency tuning, raise default concurrency from 3 to 4, and enable progressive rollout
5.2.62026-04-2276153Fix sync crash when the Zendesk API returns responses without cursor pagination keys (for example, on single-page results)
5.2.52026-04-2174696Update dependencies
5.2.42026-04-1376276Rename “concurrent workers” to “concurrent threads” in connector spec
5.2.32026-04-0776105Add token_expiry_date to complete_oauth_output_specification so it is hidden from the UI as an OAuth-managed field
5.2.22026-03-2374993Switch ticket_metric_events to time-based pagination to prevent heartbeat timeout on large datasets
5.2.12026-03-1774394Migrate to scopes object array format
5.2.02026-03-1274258Switch tickets stream to Export Search Results endpoint for concurrency and performance. Behavior change: deleted tickets are no longer returned in the tickets stream — use the new deleted_tickets stream instead. Added deleted_tickets as a suggested stream for auto-enablement on Cloud.
5.1.82026-03-1274771Upgrade CDK to 7.13.0
5.1.72026-03-1274766Promoting release candidate 5.1.7-rc.1 to a main version.
5.1.7-rc.12026-03-1074398Pin CDK to 7.8.1.post54 for regression testing of StateDelegatingStream and DeclarativeStream
5.1.62026-03-0973686Add 504 exponential backoff error handling to ticket_comments stream and API budget (10 req/min) for all incremental export streams
5.1.52026-02-2567077Add missing SLA fields (sla, group_sla, status, deleted) to ticket_metric_events schema
5.1.42026-02-2473911Update dependencies
5.1.32026-02-1773508Update dependencies
5.1.22026-02-1072624Update dependencies
5.1.12026-02-0372783Upgrade CDK version to 7.8.1
5.1.02026-02-0271752Add user-configurable page_size option for ticket_comments stream
5.0.32026-01-2872423Update breaking change deadline from Jan 31 to Jan 30
5.0.22026-01-2772380Fix OAuth race condition with concurrent token refresh
5.0.12026-01-2271714Update dependencies
5.0.02026-01-2270990Add OAuth2.0 with refresh token support. Users using OAuth must re-authenticate to use the new flow with rotating refresh tokens.
4.10.182025-12-1870717Update dependencies
4.10.172025-12-0270066Update dependencies
4.10.162025-11-1869538Update dependencies
4.10.152025-10-2968945Update dependencies
4.10.142025-10-2168408Update dependencies
4.10.132025-10-1468019Update dependencies
4.10.122025-10-0766850Update dependencies
4.10.112025-09-2466461Update dependencies
4.10.102025-09-0965729Update dependencies
4.10.92025-08-2665558Update dependencies
4.10.82025-08-2465403Update dependencies
4.10.72025-08-1064867Update dependencies
4.10.62025-08-0264366Update dependencies
4.10.52025-07-2664067Update dependencies
4.10.42025-07-2063673Update dependencies
4.10.32025-07-1263238Update dependencies
4.10.22025-07-0562691Update dependencies
4.10.12025-06-2860736Update dependencies
4.10.02025-06-2662099Promoting release candidate 4.10.0-rc.1 to a main version.
4.10.0-rc.12025-06-1761599Migrate to manifest-only format.
4.9.12025-05-1060014Update dependencies
4.9.02025-05-0556419Adapt file-transfer records to latest protocol, requires platform >= 1.7.0, destination-s3 >= 1.8.0
4.8.72025-05-0459531Update dependencies
4.8.62025-04-2658917Update dependencies
4.8.52025-04-1958547Update dependencies
4.8.42025-04-1358042Update dependencies
4.8.32025-04-0557389Update dependencies
4.8.22025-03-2955157Update dependencies
4.8.12025-03-2556405Fix empty child state migration issue
4.8.02025-03-2556354Migrate posts to low-code
4.7.22025-03-1155676Prepare posts stream for low-code migration
4.7.12025-02-2654696Update requests-mock dependency versionb
4.7.02025-02-2454656Promoting release candidate 4.7.0-rc.1 to a main version.
4.7.0-rc.12025-02-1353620Replace ZendeskSupportAuditLogsIncrementalSync with low-code DatetimeBasedCursor
4.6.02024-12-0947939Add User Identities stream
4.5.02024-12-0248761Add Categories and Sections stream
4.4.42025-02-0851943Update dependencies
4.4.32025-02-0352625Update error message during check for organization_access_enabled
4.4.22025-01-1148309Starting with this version, the Docker image is now rootless. Please note that this and future versions will not be compatible with Airbyte versions earlier than 0.64
4.4.12024-12-1348889Check if start_date exist in check operation
4.4.02024-11-1148379Make DatetimeBasedCursor syncs concurrent
4.3.32024-10-2847663Update dependencies
4.3.22024-10-2147202Update dependencies and expected records
4.3.12024-10-1246794Update dependencies
4.3.02024-10-0946096Updates TicketMetrics stream for improved reliability for long syncs, updates state cursor field to _ab_updated_at, automatically migrates legacy state
4.2.32024-10-0546408Update dependencies
4.2.22024-09-2845784Update dependencies
4.2.12024-09-1445561Update dependencies
4.2.02024-09-1044610Add Automations and Triggers stream
4.1.12024-09-0745215Update dependencies
4.1.02024-09-0645187Migrate to CDK v5
4.0.22024-08-3144965Update dependencies
4.0.12024-08-2444692Update dependencies
4.0.02024-08-1944096Stream Tags: use cursor based pagination
3.0.12024-08-1744324Update dependencies
3.0.02024-08-1343446TicketMetrics stream: updates cursor field to generated_timestamp
2.7.32024-08-1243900Update dependencies
2.7.22024-08-1043614Update dependencies
2.7.12024-08-0341799Update dependencies
2.7.02024-08-0242975Migrate to CDK v4.3.0
2.6.132024-07-3142892Update BackoffStrategy interface to be up-to-date with latest parent interface.
2.6.122024-07-2542519Update error message for permission issue.
2.6.112024-07-1842100Raise config error on 403/404 status code.
2.6.102024-07-1041436Fix unit test
2.6.92024-07-1041390Update dependencies
2.6.82024-07-0940025Update dependencies
2.6.72024-07-0941032Use latest CDK: 3.0.0
2.6.62024-06-2740592Updated to use latest CDK version, fixed cursor pagination logic
2.6.52024-05-2338607Migrate to cursor based pagination in stream Organization memberships
2.6.42024-05-2038310Fix record filter for Ticket Metrics stream
2.6.32024-05-0236669Schema descriptions
2.6.22024-02-0537761Add stop condition for Ticket Audits when recieved old records; Ignore 403 and 404 status codes.
2.6.12024-04-3037723Add %Y-%m-%dT%H:%M:%S%z to cursor_datetime_formats
2.6.02024-04-2936823Migrate to low code; Add new stream Ticket Activities
2.5.02024-04-2536388Fix data type of field in Tickets stream schema stream.
2.4.12024-04-2037450Fix parsing response for Ticket Metrics stream.
2.4.02024-04-0936897Fix long-running syncs for Ticket Metrics, Ticket Audits and Satisfaction Ratings streams.
2.3.02024-03-2636403Unpin CDK version, add record counts to state messages
2.2.82024-02-0935083Manage dependencies with Poetry.
2.2.72024-02-0534840Fix missing fields in schema
2.2.62024-01-1134064Skip 504 Error for stream Ticket Audits
2.2.52024-01-0834010Prepare for airbyte-lib
2.2.42023-12-2033680Fix pagination issue for streams related to incremental export sync
2.2.32023-12-1433435Fix 504 Error for stream Ticket Audits
2.2.22023-12-0133012Increase number of retries for backoff policy to 10
2.2.12023-11-1032440Made refactoring to improve code maintainability
2.2.02023-10-3131999Extended the CustomRoles stream schema
2.1.12023-10-2331702Base image migration: remove Dockerfile and use the python-connector-base image
2.1.02023-10-1931606Added new field reply_time_in_seconds to the Ticket Metrics stream schema
2.0.02023-09-1530440Remove stream Deleted Tickets
1.7.02023-09-1130259Add stream Deleted Tickets
1.6.02023-09-0930168Make start_date field optional
1.5.12023-09-0530142Handle non-JSON Response
1.5.02023-09-0430138Add new Streams: Article Votes, Article Comments, Article Comment Votes
1.4.02023-09-0430134Add incremental support for streams: custom Roles, Schedules, SLA Policies
1.3.02023-08-3030031Add new streams: Articles, Organization Fields
1.2.22023-08-3029998Fix typo in stream AttributeDefinitions: field condition
1.2.12023-08-3029991Remove Custom availability strategy
1.2.02023-08-2929940Add undeclared fields to schemas
1.1.12023-08-2929904Make Organizations stream incremental
1.1.02023-08-2829891Add stream UserFields
1.0.02023-07-2728774Fix retry logic & update cursor for Tickets stream
0.12.02023-08-2229697Add manage_team_members field to the Custom Roles stream
0.11.02023-08-1027208Add stream Topics
0.10.72023-08-0929256Update tooltip descriptions in spec
0.10.62023-08-0429031Reverted advancedAuth spec changes
0.10.52023-08-0128910Updated advancedAuth broken references
0.10.42023-07-2528397Handle 404 Error
0.10.32023-07-2428612Fix pagination for stream TicketMetricEvents
0.10.22023-07-1928487Remove extra page from params
0.10.12023-07-1028096Replace offset pagination with cursor pagination
0.10.02023-07-0627991Add streams: PostVotes, PostCommentVotes
0.9.02023-07-0527961Add stream: Post Comments
0.8.12023-06-2727765Bugfix: Nonetype error while syncing more then 100000 organizations
0.8.02023-06-0927156Add stream Posts
0.7.02023-06-2727436Add Ticket Skips stream
0.6.02023-06-2727450Add Skill Based Routing streams
0.5.02023-06-2627735License Update: Elv2 stream stream
0.4.02023-06-1627431Add Organization Memberships stream
0.3.12023-06-0226945Make Ticket Metrics stream to use cursor pagination
0.3.02023-05-2326347Add stream Audit Logs logs`
0.2.302023-05-2326414Added missing handlers when empty json or JSONDecodeError is received
0.2.292023-04-1825214Add missing fields to Tickets stream
0.2.282023-03-2124053Fix stream sla_policies schema data type error (events.value)
0.2.272023-03-2222817Specified date formatting in specification
0.2.262023-03-2024252Handle invalid start_date when checking connection
0.2.252023-02-2822308Add AvailabilityStrategy for all streams
0.2.242023-02-1723246Handle StartTimeTooRecent error for Tickets stream
0.2.232023-02-1523035Handle 403 Error
0.2.222023-02-1422483Fix test; handle 400 error
0.2.212023-01-2722027Set AvailabilityStrategy for streams explicitly to None
0.2.202022-12-2820900Remove synchronous time.sleep, add logging, reduce backoff time
0.2.192022-12-0919967Fix reading response for more than 100k records
0.2.182022-11-2919432Revert changes from version 0.2.15, use a test read instead
0.2.172022-11-2419792Transform ticket_comments.via ”-” to null
0.2.162022-09-2817326Migrate to per-stream states.
0.2.152022-08-0315233Added subscription plan check on streams discovery step to remove streams that are not accessible for fetch due to subscription plan restrictions
0.2.142022-07-2715036Convert ticket_audits.previous_value values to string
0.2.132022-07-2114829Convert tickets.custom_fields values to string
0.2.122022-06-3014304Fixed Pagination for Group Membership stream
0.2.112022-06-2414112Fixed “Retry-After” non integer value
0.2.102022-06-1413757Fixed the bug with TicketMetrics stream, HTTP Error 429, caused by lots of API requests
0.2.92022-05-2713261Bugfix for the unhandled ChunkedEncodingError and ConnectionError
0.2.82022-05-2013055Fixed minor issue for stream ticket_audits schema
0.2.72022-04-2712335Adding fixtures to mock time.sleep for connectors that explicitly sleep
0.2.62022-04-1912122Fixed the bug when only 100,000 Users are synced 11895 and fixed bug when start_date is not used on user stream 12059.
0.2.52022-04-0511727Fixed the bug when state was not parsed correctly
0.2.42022-04-0411688Small documentation corrections
0.2.32022-03-2311349Fixed the bug when Tickets stream didn’t return deleted records
0.2.22022-03-1711237Fixed the bug when TicketComments stream didn’t return all records
0.2.12022-03-1511162Added support of OAuth2.0 authentication method
0.2.02022-03-019456Update source to use future requests
0.1.122022-01-259785Add additional log messages
0.1.112021-12-218987Update connector fields title/description
0.1.92021-12-168616Adds Brands, CustomRoles and Schedules streams
0.1.82021-11-238168Adds TicketMetricEvents stream
0.1.72021-11-238058Added support of AccessToken authentication
0.1.62021-11-188050Fix wrong types for schemas, add TypeTransformer
0.1.52021-10-267679Add ticket_id and ticket_comments
0.1.42021-10-267377Fix initially_assigned_at type in ticket metrics
0.1.32021-10-177097Corrected the connector’s specification
0.1.22021-10-166513Fixed TicketComments stream
0.1.12021-09-025787Fixed incremental logic for the ticket_comments stream
0.1.02021-07-214861Created CDK native zendesk connector
Advanced Analytica

Most businesses are sitting on information they can’t use at speed. The people who hold it are busy, and when they leave, the knowledge goes with them. The documents are static, and the processes around them weren’t designed for AI.

Advanced Analytica works with these businesses to turn that information into structured data assets. Once they're integrated, AI systems can govern it, and the business can use it. We bring in the strategy, the specification and the AI skills to rework how the business operates.

MOVE FAST. STAY SAFE.