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. :::
-
Log in to your Zendesk account.
-
Click the Zendesk Products icon (four squares) in the top-right corner, then select Admin Center.
-
In the left navbar, click Apps and Integrations, then select APIs > Zendesk API.
-
In the Settings tab, toggle the option to enable token access.
-
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. :::
-
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.
- Register an OAuth client in Admin Center. See Registering your application with Zendesk. Note the client’s unique identifier and secret.
- Complete Zendesk’s authorization code flow with the
readscope. Includeexpires_inin 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 withoutexpires_inreturns a token you can’t refresh. The maximum value is172800(48 hours). The connector requests this value in Airbyte Cloud. - Save the
refresh_tokenfrom 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
- Log into your Airbyte Cloud account.
- Click Sources and then click + New source.
- On the Set up the source page, select Zendesk Support from the Source type dropdown.
- Enter a name for the Zendesk Support connector.
Airbyte Open Source
- Go to the Airbyte Open Source dashboard.
- Click Sources and then click + New source.
- On the Set up the source page, select Zendesk Support from the Source type dropdown.
- Enter a name for the Zendesk Support connector.
- 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.
- For Subdomain, enter your Zendesk subdomain from your account URL. For example, if your account URL is
https://MY_SUBDOMAIN.zendesk.com/, your subdomain isMY_SUBDOMAIN. - (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. - (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.
- (Optional) For Page Size (ticket_comments), enter the number of records per page for the
ticket_commentsstream. The default is 100, and the maximum is 1000. Lower values can help prevent timeouts on large Zendesk instances. - (Optional) For Tickets Search Lookback Window (days), enter how many days the
tickets_searchstream re-scans during each sync. The default is 0. This setting affects only the opt-intickets_searchstream. See Tickets stream: change tracking. - 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:
- Incremental (standard server-side, where the API returns only data updated or created since the previous sync).
- 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:
- Account Attributes (Enterprise only)
- Articles (Incremental)
- Article Votes (Incremental)
- Article Comments (Incremental)
- Article Comment Votes (Incremental)
- Article Attachments (Incremental) (Supports file transfer)
- Attribute Definitions (Enterprise only)
- Audit Logs (Incremental) (Enterprise only)
- Automations
- Brands
- Custom Roles (Client-Side Incremental)
- Groups (Client-Side Incremental)
- Group Memberships (Client-Side Incremental)
- Macros (Incremental)
- Organizations (Incremental)
- Organization Fields (Client-Side Incremental)
- Organization Memberships (Client-Side Incremental)
- Posts (Incremental)
- Post Comments (Incremental)
- Post Comment Votes (Incremental)
- Post Votes (Incremental)
- Satisfaction Ratings (Incremental)
- Schedules (Client-Side Incremental)
- Side Conversations (Client-Side Incremental) (Requires a plan that includes side conversations)
- SLA Policies (Client-Side Incremental)
- Tags
- Tickets (Incremental)
- Tickets Search (Incremental) (Opt-in)
- Deleted Tickets (Full Refresh)
- Ticket Activities (Client-Side Incremental)
- Ticket Audits (Client-Side Incremental)
- Ticket Audits per Ticket (Incremental) (Opt-in)
- Ticket Comments (Incremental)
- Ticket Fields (Client-Side Incremental)
- Ticket Forms (Client-Side Incremental) (Enterprise only)
- Ticket Metrics (Incremental)
- Ticket Events (Incremental)
- Ticket Metric Events (Incremental)
- Topics (Client-Side Incremental)
- Triggers (Client-Side Incremental)
- Ticket Skips (Client-Side Incremental)
- Users (Incremental)
- User Identities (Incremental)
- User Fields
- Categories
- Sections
Deleted records
The Zendesk Support connector fetches deleted records from these streams:
| Stream | Deletion indicator field |
|---|---|
| Brands | is_deleted |
| Deleted Tickets | All records are deleted |
| Groups | deleted |
| Organizations | deleted_at |
| Ticket Metric Events | deleted |
:::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-Afterheader 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
ticketsstream. - 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:
| Plan | Requests per minute |
|---|---|
| Team | 200 |
| Growth / Professional | 400 |
| Enterprise | 700 |
| Enterprise Plus / High Volume API add-on | 2500 |
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 theticketsstream 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.
Search index delay in tickets_search
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
| Version | Date | Pull Request | Subject |
|---|---|---|---|
| 5.7.0 | 2026-10-20 | 89571 | Add 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.3 | 2026-10-13 | 87513 | Refresh 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.2 | 2026-10-13 | 88867 | Update dependencies |
| 5.6.1 | 2026-10-06 | 84185 | Update dependencies |
| 5.6.0 | 2026-09-10 | 85760 | Raise 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.2 | 2026-08-26 | 84353 | Skip 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.1 | 2026-08-11 | 82679 | Request 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.0 | 2026-08-10 | 83812 | Promoted release candidate to GA |
| 5.5.0-rc.1 | 2026-08-03 | 81640 | Revert 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.6 | 2026-07-28 | 83194 | Update to CDK 7.23.8 (fixes AirbyteCustomCodeNotPermittedError for bundled custom components) and remove the temporary Cloud version override |
| 5.4.5 | 2026-07-28 | 1082 | Roll Cloud back to 5.4.3 — 5.4.4 is built on SDM 7.23.7, which breaks bundled custom components |
| 5.4.4 | 2026-07-28 | 83159 | Update dependencies |
| 5.4.3 | 2026-07-21 | 82661 | Update dependencies |
| 5.4.2 | 2026-07-14 | 82080 | Update dependencies |
| 5.4.1 | 2026-07-06 | 81210 | Fixed side_conversations stream: added millisecond-precision timestamp parsing for cursor field and added error handler to skip tickets returning HTTP 422 |
| 5.4.0 | 2026-07-02 | 81403 | Added ticket_events stream for Zendesk Incremental Ticket Event Export API |
| 5.3.1 | 2026-06-30 | 81305 | Update dependencies |
| 5.3.0 | 2026-06-27 | 79640 | Added side_conversations stream to retrieve Side Conversations from tickets |
| 5.2.12 | 2026-06-23 | 80725 | Update dependencies |
| 5.2.11 | 2026-06-16 | 80108 | Update dependencies |
| 5.2.10 | 2026-06-12 | 79668 | Gracefully skip streams when Zendesk returns permission-denied error instead of failing the entire sync |
| 5.2.9 | 2026-06-09 | 79583 | Update dependencies |
| 5.2.8 | 2026-06-02 | 77507 | Update dependencies |
| 5.2.7 | 2026-05-15 | 78120 | Promoted release candidate to GA |
| 5.2.7-rc.4 | 2026-05-07 | 77857 | Step 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.3 | 2026-05-05 | 77784 | Restore 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.2 | 2026-04-28 | 77548 | Activate the tier-aware HTTP API budget driven by subscription_tier and raise default concurrency from 4 to 5 |
| 5.2.7-rc.1 | 2026-04-23 | 76953 | Add 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.6 | 2026-04-22 | 76153 | Fix sync crash when the Zendesk API returns responses without cursor pagination keys (for example, on single-page results) |
| 5.2.5 | 2026-04-21 | 74696 | Update dependencies |
| 5.2.4 | 2026-04-13 | 76276 | Rename “concurrent workers” to “concurrent threads” in connector spec |
| 5.2.3 | 2026-04-07 | 76105 | Add token_expiry_date to complete_oauth_output_specification so it is hidden from the UI as an OAuth-managed field |
| 5.2.2 | 2026-03-23 | 74993 | Switch ticket_metric_events to time-based pagination to prevent heartbeat timeout on large datasets |
| 5.2.1 | 2026-03-17 | 74394 | Migrate to scopes object array format |
| 5.2.0 | 2026-03-12 | 74258 | Switch 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.8 | 2026-03-12 | 74771 | Upgrade CDK to 7.13.0 |
| 5.1.7 | 2026-03-12 | 74766 | Promoting release candidate 5.1.7-rc.1 to a main version. |
| 5.1.7-rc.1 | 2026-03-10 | 74398 | Pin CDK to 7.8.1.post54 for regression testing of StateDelegatingStream and DeclarativeStream |
| 5.1.6 | 2026-03-09 | 73686 | Add 504 exponential backoff error handling to ticket_comments stream and API budget (10 req/min) for all incremental export streams |
| 5.1.5 | 2026-02-25 | 67077 | Add missing SLA fields (sla, group_sla, status, deleted) to ticket_metric_events schema |
| 5.1.4 | 2026-02-24 | 73911 | Update dependencies |
| 5.1.3 | 2026-02-17 | 73508 | Update dependencies |
| 5.1.2 | 2026-02-10 | 72624 | Update dependencies |
| 5.1.1 | 2026-02-03 | 72783 | Upgrade CDK version to 7.8.1 |
| 5.1.0 | 2026-02-02 | 71752 | Add user-configurable page_size option for ticket_comments stream |
| 5.0.3 | 2026-01-28 | 72423 | Update breaking change deadline from Jan 31 to Jan 30 |
| 5.0.2 | 2026-01-27 | 72380 | Fix OAuth race condition with concurrent token refresh |
| 5.0.1 | 2026-01-22 | 71714 | Update dependencies |
| 5.0.0 | 2026-01-22 | 70990 | Add OAuth2.0 with refresh token support. Users using OAuth must re-authenticate to use the new flow with rotating refresh tokens. |
| 4.10.18 | 2025-12-18 | 70717 | Update dependencies |
| 4.10.17 | 2025-12-02 | 70066 | Update dependencies |
| 4.10.16 | 2025-11-18 | 69538 | Update dependencies |
| 4.10.15 | 2025-10-29 | 68945 | Update dependencies |
| 4.10.14 | 2025-10-21 | 68408 | Update dependencies |
| 4.10.13 | 2025-10-14 | 68019 | Update dependencies |
| 4.10.12 | 2025-10-07 | 66850 | Update dependencies |
| 4.10.11 | 2025-09-24 | 66461 | Update dependencies |
| 4.10.10 | 2025-09-09 | 65729 | Update dependencies |
| 4.10.9 | 2025-08-26 | 65558 | Update dependencies |
| 4.10.8 | 2025-08-24 | 65403 | Update dependencies |
| 4.10.7 | 2025-08-10 | 64867 | Update dependencies |
| 4.10.6 | 2025-08-02 | 64366 | Update dependencies |
| 4.10.5 | 2025-07-26 | 64067 | Update dependencies |
| 4.10.4 | 2025-07-20 | 63673 | Update dependencies |
| 4.10.3 | 2025-07-12 | 63238 | Update dependencies |
| 4.10.2 | 2025-07-05 | 62691 | Update dependencies |
| 4.10.1 | 2025-06-28 | 60736 | Update dependencies |
| 4.10.0 | 2025-06-26 | 62099 | Promoting release candidate 4.10.0-rc.1 to a main version. |
| 4.10.0-rc.1 | 2025-06-17 | 61599 | Migrate to manifest-only format. |
| 4.9.1 | 2025-05-10 | 60014 | Update dependencies |
| 4.9.0 | 2025-05-05 | 56419 | Adapt file-transfer records to latest protocol, requires platform >= 1.7.0, destination-s3 >= 1.8.0 |
| 4.8.7 | 2025-05-04 | 59531 | Update dependencies |
| 4.8.6 | 2025-04-26 | 58917 | Update dependencies |
| 4.8.5 | 2025-04-19 | 58547 | Update dependencies |
| 4.8.4 | 2025-04-13 | 58042 | Update dependencies |
| 4.8.3 | 2025-04-05 | 57389 | Update dependencies |
| 4.8.2 | 2025-03-29 | 55157 | Update dependencies |
| 4.8.1 | 2025-03-25 | 56405 | Fix empty child state migration issue |
| 4.8.0 | 2025-03-25 | 56354 | Migrate posts to low-code |
| 4.7.2 | 2025-03-11 | 55676 | Prepare posts stream for low-code migration |
| 4.7.1 | 2025-02-26 | 54696 | Update requests-mock dependency versionb |
| 4.7.0 | 2025-02-24 | 54656 | Promoting release candidate 4.7.0-rc.1 to a main version. |
| 4.7.0-rc.1 | 2025-02-13 | 53620 | Replace ZendeskSupportAuditLogsIncrementalSync with low-code DatetimeBasedCursor |
| 4.6.0 | 2024-12-09 | 47939 | Add User Identities stream |
| 4.5.0 | 2024-12-02 | 48761 | Add Categories and Sections stream |
| 4.4.4 | 2025-02-08 | 51943 | Update dependencies |
| 4.4.3 | 2025-02-03 | 52625 | Update error message during check for organization_access_enabled |
| 4.4.2 | 2025-01-11 | 48309 | Starting 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.1 | 2024-12-13 | 48889 | Check if start_date exist in check operation |
| 4.4.0 | 2024-11-11 | 48379 | Make DatetimeBasedCursor syncs concurrent |
| 4.3.3 | 2024-10-28 | 47663 | Update dependencies |
| 4.3.2 | 2024-10-21 | 47202 | Update dependencies and expected records |
| 4.3.1 | 2024-10-12 | 46794 | Update dependencies |
| 4.3.0 | 2024-10-09 | 46096 | Updates TicketMetrics stream for improved reliability for long syncs, updates state cursor field to _ab_updated_at, automatically migrates legacy state |
| 4.2.3 | 2024-10-05 | 46408 | Update dependencies |
| 4.2.2 | 2024-09-28 | 45784 | Update dependencies |
| 4.2.1 | 2024-09-14 | 45561 | Update dependencies |
| 4.2.0 | 2024-09-10 | 44610 | Add Automations and Triggers stream |
| 4.1.1 | 2024-09-07 | 45215 | Update dependencies |
| 4.1.0 | 2024-09-06 | 45187 | Migrate to CDK v5 |
| 4.0.2 | 2024-08-31 | 44965 | Update dependencies |
| 4.0.1 | 2024-08-24 | 44692 | Update dependencies |
| 4.0.0 | 2024-08-19 | 44096 | Stream Tags: use cursor based pagination |
| 3.0.1 | 2024-08-17 | 44324 | Update dependencies |
| 3.0.0 | 2024-08-13 | 43446 | TicketMetrics stream: updates cursor field to generated_timestamp |
| 2.7.3 | 2024-08-12 | 43900 | Update dependencies |
| 2.7.2 | 2024-08-10 | 43614 | Update dependencies |
| 2.7.1 | 2024-08-03 | 41799 | Update dependencies |
| 2.7.0 | 2024-08-02 | 42975 | Migrate to CDK v4.3.0 |
| 2.6.13 | 2024-07-31 | 42892 | Update BackoffStrategy interface to be up-to-date with latest parent interface. |
| 2.6.12 | 2024-07-25 | 42519 | Update error message for permission issue. |
| 2.6.11 | 2024-07-18 | 42100 | Raise config error on 403/404 status code. |
| 2.6.10 | 2024-07-10 | 41436 | Fix unit test |
| 2.6.9 | 2024-07-10 | 41390 | Update dependencies |
| 2.6.8 | 2024-07-09 | 40025 | Update dependencies |
| 2.6.7 | 2024-07-09 | 41032 | Use latest CDK: 3.0.0 |
| 2.6.6 | 2024-06-27 | 40592 | Updated to use latest CDK version, fixed cursor pagination logic |
| 2.6.5 | 2024-05-23 | 38607 | Migrate to cursor based pagination in stream Organization memberships |
| 2.6.4 | 2024-05-20 | 38310 | Fix record filter for Ticket Metrics stream |
| 2.6.3 | 2024-05-02 | 36669 | Schema descriptions |
| 2.6.2 | 2024-02-05 | 37761 | Add stop condition for Ticket Audits when recieved old records; Ignore 403 and 404 status codes. |
| 2.6.1 | 2024-04-30 | 37723 | Add %Y-%m-%dT%H:%M:%S%z to cursor_datetime_formats |
| 2.6.0 | 2024-04-29 | 36823 | Migrate to low code; Add new stream Ticket Activities |
| 2.5.0 | 2024-04-25 | 36388 | Fix data type of field in Tickets stream schema stream. |
| 2.4.1 | 2024-04-20 | 37450 | Fix parsing response for Ticket Metrics stream. |
| 2.4.0 | 2024-04-09 | 36897 | Fix long-running syncs for Ticket Metrics, Ticket Audits and Satisfaction Ratings streams. |
| 2.3.0 | 2024-03-26 | 36403 | Unpin CDK version, add record counts to state messages |
| 2.2.8 | 2024-02-09 | 35083 | Manage dependencies with Poetry. |
| 2.2.7 | 2024-02-05 | 34840 | Fix missing fields in schema |
| 2.2.6 | 2024-01-11 | 34064 | Skip 504 Error for stream Ticket Audits |
| 2.2.5 | 2024-01-08 | 34010 | Prepare for airbyte-lib |
| 2.2.4 | 2023-12-20 | 33680 | Fix pagination issue for streams related to incremental export sync |
| 2.2.3 | 2023-12-14 | 33435 | Fix 504 Error for stream Ticket Audits |
| 2.2.2 | 2023-12-01 | 33012 | Increase number of retries for backoff policy to 10 |
| 2.2.1 | 2023-11-10 | 32440 | Made refactoring to improve code maintainability |
| 2.2.0 | 2023-10-31 | 31999 | Extended the CustomRoles stream schema |
| 2.1.1 | 2023-10-23 | 31702 | Base image migration: remove Dockerfile and use the python-connector-base image |
| 2.1.0 | 2023-10-19 | 31606 | Added new field reply_time_in_seconds to the Ticket Metrics stream schema |
| 2.0.0 | 2023-09-15 | 30440 | Remove stream Deleted Tickets |
| 1.7.0 | 2023-09-11 | 30259 | Add stream Deleted Tickets |
| 1.6.0 | 2023-09-09 | 30168 | Make start_date field optional |
| 1.5.1 | 2023-09-05 | 30142 | Handle non-JSON Response |
| 1.5.0 | 2023-09-04 | 30138 | Add new Streams: Article Votes, Article Comments, Article Comment Votes |
| 1.4.0 | 2023-09-04 | 30134 | Add incremental support for streams: custom Roles, Schedules, SLA Policies |
| 1.3.0 | 2023-08-30 | 30031 | Add new streams: Articles, Organization Fields |
| 1.2.2 | 2023-08-30 | 29998 | Fix typo in stream AttributeDefinitions: field condition |
| 1.2.1 | 2023-08-30 | 29991 | Remove Custom availability strategy |
| 1.2.0 | 2023-08-29 | 29940 | Add undeclared fields to schemas |
| 1.1.1 | 2023-08-29 | 29904 | Make Organizations stream incremental |
| 1.1.0 | 2023-08-28 | 29891 | Add stream UserFields |
| 1.0.0 | 2023-07-27 | 28774 | Fix retry logic & update cursor for Tickets stream |
| 0.12.0 | 2023-08-22 | 29697 | Add manage_team_members field to the Custom Roles stream |
| 0.11.0 | 2023-08-10 | 27208 | Add stream Topics |
| 0.10.7 | 2023-08-09 | 29256 | Update tooltip descriptions in spec |
| 0.10.6 | 2023-08-04 | 29031 | Reverted advancedAuth spec changes |
| 0.10.5 | 2023-08-01 | 28910 | Updated advancedAuth broken references |
| 0.10.4 | 2023-07-25 | 28397 | Handle 404 Error |
| 0.10.3 | 2023-07-24 | 28612 | Fix pagination for stream TicketMetricEvents |
| 0.10.2 | 2023-07-19 | 28487 | Remove extra page from params |
| 0.10.1 | 2023-07-10 | 28096 | Replace offset pagination with cursor pagination |
| 0.10.0 | 2023-07-06 | 27991 | Add streams: PostVotes, PostCommentVotes |
| 0.9.0 | 2023-07-05 | 27961 | Add stream: Post Comments |
| 0.8.1 | 2023-06-27 | 27765 | Bugfix: Nonetype error while syncing more then 100000 organizations |
| 0.8.0 | 2023-06-09 | 27156 | Add stream Posts |
| 0.7.0 | 2023-06-27 | 27436 | Add Ticket Skips stream |
| 0.6.0 | 2023-06-27 | 27450 | Add Skill Based Routing streams |
| 0.5.0 | 2023-06-26 | 27735 | License Update: Elv2 stream stream |
| 0.4.0 | 2023-06-16 | 27431 | Add Organization Memberships stream |
| 0.3.1 | 2023-06-02 | 26945 | Make Ticket Metrics stream to use cursor pagination |
| 0.3.0 | 2023-05-23 | 26347 | Add stream Audit Logs logs` |
| 0.2.30 | 2023-05-23 | 26414 | Added missing handlers when empty json or JSONDecodeError is received |
| 0.2.29 | 2023-04-18 | 25214 | Add missing fields to Tickets stream |
| 0.2.28 | 2023-03-21 | 24053 | Fix stream sla_policies schema data type error (events.value) |
| 0.2.27 | 2023-03-22 | 22817 | Specified date formatting in specification |
| 0.2.26 | 2023-03-20 | 24252 | Handle invalid start_date when checking connection |
| 0.2.25 | 2023-02-28 | 22308 | Add AvailabilityStrategy for all streams |
| 0.2.24 | 2023-02-17 | 23246 | Handle StartTimeTooRecent error for Tickets stream |
| 0.2.23 | 2023-02-15 | 23035 | Handle 403 Error |
| 0.2.22 | 2023-02-14 | 22483 | Fix test; handle 400 error |
| 0.2.21 | 2023-01-27 | 22027 | Set AvailabilityStrategy for streams explicitly to None |
| 0.2.20 | 2022-12-28 | 20900 | Remove synchronous time.sleep, add logging, reduce backoff time |
| 0.2.19 | 2022-12-09 | 19967 | Fix reading response for more than 100k records |
| 0.2.18 | 2022-11-29 | 19432 | Revert changes from version 0.2.15, use a test read instead |
| 0.2.17 | 2022-11-24 | 19792 | Transform ticket_comments.via ”-” to null |
| 0.2.16 | 2022-09-28 | 17326 | Migrate to per-stream states. |
| 0.2.15 | 2022-08-03 | 15233 | Added subscription plan check on streams discovery step to remove streams that are not accessible for fetch due to subscription plan restrictions |
| 0.2.14 | 2022-07-27 | 15036 | Convert ticket_audits.previous_value values to string |
| 0.2.13 | 2022-07-21 | 14829 | Convert tickets.custom_fields values to string |
| 0.2.12 | 2022-06-30 | 14304 | Fixed Pagination for Group Membership stream |
| 0.2.11 | 2022-06-24 | 14112 | Fixed “Retry-After” non integer value |
| 0.2.10 | 2022-06-14 | 13757 | Fixed the bug with TicketMetrics stream, HTTP Error 429, caused by lots of API requests |
| 0.2.9 | 2022-05-27 | 13261 | Bugfix for the unhandled ChunkedEncodingError and ConnectionError |
| 0.2.8 | 2022-05-20 | 13055 | Fixed minor issue for stream ticket_audits schema |
| 0.2.7 | 2022-04-27 | 12335 | Adding fixtures to mock time.sleep for connectors that explicitly sleep |
| 0.2.6 | 2022-04-19 | 12122 | Fixed 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.5 | 2022-04-05 | 11727 | Fixed the bug when state was not parsed correctly |
| 0.2.4 | 2022-04-04 | 11688 | Small documentation corrections |
| 0.2.3 | 2022-03-23 | 11349 | Fixed the bug when Tickets stream didn’t return deleted records |
| 0.2.2 | 2022-03-17 | 11237 | Fixed the bug when TicketComments stream didn’t return all records |
| 0.2.1 | 2022-03-15 | 11162 | Added support of OAuth2.0 authentication method |
| 0.2.0 | 2022-03-01 | 9456 | Update source to use future requests |
| 0.1.12 | 2022-01-25 | 9785 | Add additional log messages |
| 0.1.11 | 2021-12-21 | 8987 | Update connector fields title/description |
| 0.1.9 | 2021-12-16 | 8616 | Adds Brands, CustomRoles and Schedules streams |
| 0.1.8 | 2021-11-23 | 8168 | Adds TicketMetricEvents stream |
| 0.1.7 | 2021-11-23 | 8058 | Added support of AccessToken authentication |
| 0.1.6 | 2021-11-18 | 8050 | Fix wrong types for schemas, add TypeTransformer |
| 0.1.5 | 2021-10-26 | 7679 | Add ticket_id and ticket_comments |
| 0.1.4 | 2021-10-26 | 7377 | Fix initially_assigned_at type in ticket metrics |
| 0.1.3 | 2021-10-17 | 7097 | Corrected the connector’s specification |
| 0.1.2 | 2021-10-16 | 6513 | Fixed TicketComments stream |
| 0.1.1 | 2021-09-02 | 5787 | Fixed incremental logic for the ticket_comments stream |
| 0.1.0 | 2021-07-21 | 4861 | Created CDK native zendesk connector |