Skip to content

Stacksync × Supabase Miami: AI-Native OperationsOct 13Reserve your spot

Database / Business productivity · Two-way sync platform

Airtable and Zendesk integration — two-way sync

Keep supported Airtable and Zendesk records aligned with two-way sync. Give each team access to current data while controlling which system can update each field.

  • Field mappings and sync direction under your control
  • Inspect and resolve record errors in one dashboard
Two-way sync for supported objects
stacksync.com
Airtable
Zendesk
Explore record coverage

Built for teams where self-serve, reliability and scale matter

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo

Example workflow

Support case or ticket reporting workflow

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Starting eventA change involving the proposed support case or ticket table in Airtable or Zendesk Tickets needs a defined result in the other system.

  1. Start with the proposed support case or ticket table in Airtable and Zendesk Tickets. Use the record-matching and field-ownership rules from your mapping worksheet.

  2. Resolve requester, organization, team, and status references before ticket updates.

  3. Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

What to verifyTest a merged ticket, a private note, a reopened case, and an attachment with restricted access.

Review records and field ownership

Mapping essentials

Records and field ownership

Match records by stable IDs and assign an owner for each field. The record notes identify the coverage to check.

Download the mapping worksheet

CSV · No email required

Example record relationships between Airtable and Zendesk
Airtable recordZendesk recordRecord matchingField ownership
Proposed support case or ticket tableProposed table; choose its name and schema.Reporting datasetTicketsDocumented record: SupportedRetain the ticket ID and distinguish parent tickets, follow-ups, and merged cases.Agree which queue controls status and assignee; keep private comments distinct from public replies.
AttachmentsDocumented record: See connector requirementsRecord matchingAttachmentsDocumented record: :clock1: On RequestKeep file/object ID, container, and version. A path can change and a filename can repeat.Separate document content, metadata, and sharing permissions; a metadata sync does not imply file transfer or ACL replication.
Proposed company tableProposed table; choose its name and schema.Reporting datasetOrganizationsDocumented record: :clock1: On RequestRetain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient.Assign ownership separately for relationship details and finance-controlled billing details.

Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.

Why teams connect Airtable and Zendesk

Put your Airtable and Zendesk data to work

Start with the work your team needs to complete: keep records up to date, make operational data available for reporting, or move data to a new system. Choose one Airtable and Zendesk workflow to test, define what success looks like, and decide who handles failed updates.

  • Build a product feedback database from Zendesk Tickets without exporting CSVs.

  • Coordinate cross-team work on escalations using Airtable Linked records tied to live ticket status.

  • Audit Ticket Forms usage and ticket volume by Organization in a shared Airtable Base.

What records can you sync?

Start with the records your workflow needs. Check each system’s read and write requirements before mapping fields.

Airtable

Read and write support varies by record

Record types covered in the setup guide

Record typesCoverage and requirements
  • Records
  • Attachments
  • Formula fields
See connector requirements. Confirm field permissions and sync direction.

Read the Airtable connector guide

Zendesk

Read and write support varies by record

Record types covered in the setup guide

Record typesCoverage and requirements
  • Tickets
  • Tickets Comments
  • Users
✅ Supported. Confirm field permissions and sync direction.
  • Organizations
  • Attachments
  • Ticket Forms
:clock1: On Request. Confirm field permissions and sync direction.

Read the Zendesk connector guide

Connection essentials

Review how each system connects, detects changes, and permits access to your records.

View setup requirements and limits
Connection requirementAirtableZendesk
Integration interfaceREST API (per-base Web API plus metadata and webhooks endpoints)REST API
AuthenticationOAuthOAuth app authorization
Change detectionThe connector uses incremental updates.The saved Stacksync guide does not specify the change-detection mechanism.
Read accessAvailable for supported recordsAvailable for supported records
Write accessAvailable for supported recordsAvailable for supported records

Enterprise controls

Security and control for your integrations

Explore security controls

Compliance and data transfers

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

  • SOC 2 Type II
  • ISO 27001
  • HIPAA BAA
  • GDPR
  • CCPA
  • DPF US-EU-UK-CH

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Record-level recovery

Inspect sync errors and use retry and revert controls to resolve failed updates.

Read the recovery guide

Implementation

Technical reference

Review setup, record relationships, testing, and recovery for your implementation.

Authentication, permissions and API limits

Connection requirements and limits

Airtable
Integration interface
REST API (per-base Web API plus metadata and webhooks endpoints)
Authentication
OAuth (Airtable OAuth grant to specific bases or all resources); the authorizing user must have a `creator` role, since only creator roles can create webhooks
Change detection
The connector uses incremental updates. Formula fields do not emit ordinary change notifications and are refreshed hourly.
Read access
Available for supported records
Write access
Available for supported records
Setup requirements
  • Authorize access to the intended bases through OAuth with an Airtable creator role, which is required to create webhooks.
  • Check formula and attachment fields separately from ordinary editable fields.
Limitations to check
  • Formula fields are refreshed hourly, so ordinary record-change timing cannot be promised for computed values.
  • API request limits constrain throughput; measure completion time with the planned record volume.
Technical documentation

Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.

Airtable setup guide
Zendesk
Integration interface
REST API
Authentication
OAuth app authorization: enter your Zendesk subdomain (from {sub_domain_name}.zendesk.com) in Stacksync Connections and click "Authorize App"
Change detection
The saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.
Read access
Available for supported records
Write access
Available for supported records
Setup requirements
  • Provide the Zendesk subdomain in the Stacksync connection form and authorize the app.
  • Request additional access before relying on Organizations, Attachments, or Ticket Forms.
Limitations to check
  • Organizations, Attachments, and Ticket Forms are listed as On Request.
Technical documentation

Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.

Zendesk setup guide

Prepare Airtable and Zendesk access

Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.

Airtable setup checklist
  • Authorize access to the intended bases through OAuth with an Airtable creator role, which is required to create webhooks.
  • Check formula and attachment fields separately from ordinary editable fields.

Setup guides: Authorize Airtable

Zendesk setup checklist
  • Provide the Zendesk subdomain in the Stacksync connection form and authorize the app.
  • Request additional access before relying on Organizations, Attachments, or Ticket Forms.

Setup guides: Authorize Zendesk

Prepare to go live

Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.

Use the Airtable and Zendesk planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

See Stacksync in action · Review current pricing

Record identity and field ownership

Keep each record tied to its source ID. Use the references below to choose field owners and preserve relationships between records.

Download the mapping worksheet · CSV, no email required

Reporting dataset

Proposed support case or ticket table in Airtable (choose its name) / Tickets

Plan a support case or ticket dataset while preserving its source meaning.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Airtable
Your database schema
Zendesk
Documented record · ✅ Supported
Record identity
Retain the ticket ID and distinguish parent tickets, follow-ups, and merged cases.
Field ownership
Agree which queue controls status and assignee; keep private comments distinct from public replies.

Fields to include

  • Source ticket ID
  • Requester reference
  • Status
  • Priority
  • Assigned team
Record dependencies
Resolve requester, organization, team, and status references before ticket updates.
Validation
Test a merged ticket, a private note, a reopened case, and an attachment with restricted access.
Recovery
Check whether a reply or notification was already sent before replaying ticket actions.

References: Zendesk: Tickets documentation

Record matching

Attachments / Attachments

Compare whether Airtable Attachments and Zendesk Attachments describe the same file or document metadata in your business.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Airtable
Documented record · See connector requirements
Zendesk
Documented record · :clock1: On Request
Record identity
Keep file/object ID, container, and version. A path can change and a filename can repeat.
Field ownership
Separate document content, metadata, and sharing permissions; a metadata sync does not imply file transfer or ACL replication.

Fields to include

  • Source file ID
  • Container reference
  • Version
  • Metadata
  • Access classification
Record dependencies
Resolve folder/container and parent-record references before attaching metadata.
Validation
Test a renamed file, a new version, a moved folder, and an access-restricted document.
Recovery
Check the current file version and destination access before retrying transfer or metadata updates.

References: Airtable: Attachments documentationZendesk: Attachments documentation

Reporting dataset

Proposed company table in Airtable (choose its name) / Organizations

Plan a company dataset while preserving its source meaning.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Airtable
Your database schema
Zendesk
Documented record · :clock1: On Request
Record identity
Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient.
Field ownership
Assign ownership separately for relationship details and finance-controlled billing details.

Fields to include

  • Source record ID
  • Legal or display name
  • Business-unit reference
  • Lifecycle status
Record dependencies
Resolve parent organizations, business units, and currency references before dependent transactions.
Validation
Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.
Recovery
Repair the cross-system ID relationship before retrying dependent records; do not merge companies solely to remove a sync error.

References: Zendesk: Organizations documentation

Reporting dataset

Proposed application user or identity table in Airtable (choose its name) / Users

Plan a application user or identity dataset while preserving its source meaning.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Airtable
Your database schema
Zendesk
Documented record · ✅ Supported
Record identity
Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact.
Field ownership
Identity and application owners approve account lifecycle and access changes; synchronize only approved attributes.

Fields to include

  • Source user ID
  • Tenant reference
  • Account status
  • Group references
Record dependencies
Resolve tenant and group references and establish a protected administrative-account policy.
Validation
Test a renamed login, disabled account, missing group, and a user existing in two tenants.
Recovery
Review access impact before retrying a lifecycle change; reconcile current identity state and retain an approval trail.

References: Zendesk: Users documentation

Reporting dataset

Proposed file or document metadata table in Airtable (choose its name) / Attachments

Plan a file or document metadata dataset while preserving its source meaning.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Airtable
Your database schema
Zendesk
Documented record · :clock1: On Request
Record identity
Keep file/object ID, container, and version. A path can change and a filename can repeat.
Field ownership
Separate document content, metadata, and sharing permissions; a metadata sync does not imply file transfer or ACL replication.

Fields to include

  • Source file ID
  • Container reference
  • Version
  • Metadata
  • Access classification
Record dependencies
Resolve folder/container and parent-record references before attaching metadata.
Validation
Test a renamed file, a new version, a moved folder, and an access-restricted document.
Recovery
Check the current file version and destination access before retrying transfer or metadata updates.

References: Zendesk: Attachments documentation

Compare integration approaches

Use Airtable Proposed support case or ticket table in Airtable (choose its name) and Zendesk Tickets for the first pilot. Verify its identity and permitted direction, then add dependent records only when the acceptance checks pass.

Stacksync managed sync

Best fit
Two-way sync for supported objects. Choose the records, writable fields, and permissions for your workflow.
Operating responsibility
Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose
Check record matching: Retain the ticket ID and distinguish parent tickets, follow-ups, and merged cases. Verify field coverage, deletion handling, and how changes are detected.

Native vendor integration

Best fit
A vendor-built integration may fit if it supports your Airtable and Zendesk record types.
Operating responsibility
Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose
First check whether either vendor offers this integration. If available, verify Proposed support case or ticket table in Airtable (choose its name) / Tickets, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit
Consider when Airtable and Zendesk need a transformation, approval, or action outside a direct record sync.
Operating responsibility
Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose
Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery.

File or scheduled snapshot

Best fit
Consider for a one-time Airtable / Zendesk migration or a reporting need with an explicit freshness window.
Operating responsibility
Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose
Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.

Workflow scenarios and expected results

Support case or ticket reporting workflow

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Starting event: A change to the selected Proposed support case or ticket table in Airtable (choose its name) or Tickets record needs a defined result in the other system.

  1. Start with Airtable Proposed support case or ticket table in Airtable (choose its name) and Zendesk Tickets. Use the record-matching and field-ownership rules from your mapping worksheet.
  2. Resolve requester, organization, team, and status references before ticket updates.
  3. Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test a merged ticket, a private note, a reopened case, and an attachment with restricted access.

If it fails: Check whether a reply or notification was already sent before replaying ticket actions.

File or document metadata sync test

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Starting event: A change to the selected Attachments or Attachments record needs a defined result in the other system.

  1. Start with Airtable Attachments and Zendesk Attachments. Use the record-matching and field-ownership rules from your mapping worksheet.
  2. Resolve folder/container and parent-record references before attaching metadata.
  3. Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test a renamed file, a new version, a moved folder, and an access-restricted document.

If it fails: Check the current file version and destination access before retrying transfer or metadata updates.

Company reporting workflow

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Starting event: A change to the selected Proposed company table in Airtable (choose its name) or Organizations record needs a defined result in the other system.

  1. Start with Airtable Proposed company table in Airtable (choose its name) and Zendesk Organizations. Use the record-matching and field-ownership rules from your mapping worksheet.
  2. Resolve parent organizations, business units, and currency references before dependent transactions.
  3. Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.

If it fails: Repair the cross-system ID relationship before retrying dependent records; do not merge companies solely to remove a sync error.

Define an explicit handoff between Airtable and Zendesk

Validate the selected objects and operations even where connector-level direction is documented.

Starting event: A business event involving Attachments needs a defined response involving Tickets or Users.

  1. Document what the source event means and which destination record or action should respond. A similar name does not establish a shared entity.
  2. Retain separate IDs and choose whether the destination is a report, a new work item, or a change to an existing record.
  3. Assign an approval owner and a duplicate-detection rule before running an action. Use a custom workflow only after its endpoint support is confirmed.

Expected result: An example input has an unambiguous destination and expected result; repeated delivery produces only the intended change.

If it fails: Resolve missing identity or ambiguous business meaning before retrying; route unsupported operations to the implementation owner.

Initial load and acceptance testing

Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.

Proposed support case or ticket table in Airtable (choose its name) / Tickets

Test case

Test a merged ticket, a private note, a reopened case, and an attachment with restricted access.

Expected result

The expected support case or ticket relationship is preserved with no duplicate action or unintended write.

Attachments / Attachments

Test case

Test a renamed file, a new version, a moved folder, and an access-restricted document.

Expected result

The expected file or document metadata relationship is preserved with no duplicate action or unintended write.

Proposed company table in Airtable (choose its name) / Organizations

Test case

Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.

Expected result

The expected company relationship is preserved with no duplicate action or unintended write.

Proposed application user or identity table in Airtable (choose its name) / Users

Test case

Test a renamed login, disabled account, missing group, and a user existing in two tenants.

Expected result

The expected application user or identity relationship is preserved with no duplicate action or unintended write.

Direction and permissions

Test case

Check that each connected account can read and write the chosen objects. Exercise both directions with a test record before enabling production changes.

Expected result

Only an approved, supported direction and permitted fields are written.

Freshness and reconciliation

Test case

Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.

Expected result

The process meets its agreed freshness target and reconciliation has no unexplained differences.

Failed updates, retries and recovery

Start with the failed record and the destination error, then inspect the source value, field requirements, and access.

Rejected or repeated support case or ticket change

Investigate

Inspect Airtable Proposed support case or ticket table in Airtable (choose its name) and Zendesk Tickets, their IDs, and the destination error.

Next action

Check whether a reply or notification was already sent before replaying ticket actions.

Rejected or repeated file or document metadata change

Investigate

Inspect Airtable Attachments and Zendesk Attachments, their IDs, and the destination error.

Next action

Check the current file version and destination access before retrying transfer or metadata updates.

Rejected or repeated company change

Investigate

Inspect Airtable Proposed company table in Airtable (choose its name) and Zendesk Organizations, their IDs, and the destination error.

Next action

Repair the cross-system ID relationship before retrying dependent records; do not merge companies solely to remove a sync error.

A record type or update is unavailable

Investigate

Check the Airtable and Zendesk connector guides, account permissions, and any operations marked On Request.

Next action

Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.

Source and destination disagree after a retry

Investigate

Compare current source values, destination validation, identity mappings, and any side effects already completed.

Next action

Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.

Read the Stacksync issues dashboard guide for retry and revert behavior.

Change detection and update delivery

How updates move between Airtable and Zendesk

See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.

Airtable Zendesk Timing depends on the connected systems

Detect changesThe connector uses incremental updates. Formula fields do not emit ordinary change notifications and are refreshed hourly.

Apply updatesSelected writable fields update in Zendesk. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.

Zendesk Airtable Timing depends on the connected systems

Detect changesThe saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.

Apply updatesSelected writable fields update in Airtable. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.

Update timing and record limits
  • Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
  • Formula fields are refreshed hourly, so ordinary record-change timing cannot be promised for computed values.
  • API request limits constrain throughput; measure completion time with the planned record volume.
FAQ

Airtable and Zendesk integration FAQ

Further reading

Guides and resources

Next step

See your workflow in Stacksync

Walk through your Airtable and Zendesk records, field mappings, and requirements with an integration engineer.

See Stacksync in action Explore plans and pricing