MotherDuck
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| See connector requirements. Confirm field permissions and sync direction. |
Data warehouse / Business productivity · Two-way sync platform
MotherDuck and Zendesk integration — two-way sync
Keep supported MotherDuck 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
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 MotherDuck or Zendesk Tickets needs a defined result in the other system.
Start with the proposed support case or ticket table in MotherDuck and Zendesk Tickets. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve requester, organization, team, and status references before ticket updates.
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 ownershipMapping 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 worksheetCSV · No email required
| MotherDuck record | Zendesk record | Record matching | Field ownership |
|---|---|---|---|
| Proposed support case or ticket tableProposed table; choose its name and schema.Reporting dataset | TicketsDocumented record: Supported | Retain 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. |
| Proposed company tableProposed table; choose its name and schema.Reporting dataset | OrganizationsDocumented record: :clock1: On Request | 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. | Assign ownership separately for relationship details and finance-controlled billing details. |
| Proposed application user or identity tableProposed table; choose its name and schema.Reporting dataset | UsersDocumented record: Supported | Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact. | Identity and application owners approve account lifecycle and access changes; synchronize only approved attributes. |
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 MotherDuck and Zendesk
Put your MotherDuck 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 MotherDuck and Zendesk workflow to test, define what success looks like, and decide who handles failed updates.
Land CRM and operational database records in MotherDuck so a small team gets warehouse-style analytics without cluster management
Sync modeled MotherDuck tables outward to operational tools for activation
Sync tickets, users, and organizations into Postgres so support analytics run on SQL instead of repeated API pulls.
Write CRM account tier, owner, and renewal data onto Zendesk organizations and ticket fields so agents see context in the ticket.
What records can you sync?
Start with the records your workflow needs. Check each system’s read and write requirements before mapping fields.
Zendesk
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| ✅ Supported. Confirm field permissions and sync direction. |
| :clock1: On Request. Confirm field permissions and sync direction. |
Connection essentials
Review how each system connects, detects changes, and permits access to your records.
View setup requirements and limits| Connection requirement | MotherDuck | Zendesk |
|---|---|---|
| Integration interface | SQL through DuckDB clients and drivers using a MotherDuck (md:) connection | REST API |
| Authentication | Access token created in MotherDuck | OAuth app authorization |
| Change detection | The saved Stacksync guide does not specify the change-detection mechanism. | The saved Stacksync guide does not specify the change-detection mechanism. |
| Read access | Available for supported records | Available for supported records |
| Write access | Available for supported records | Available for supported records |
Enterprise controls
Security and control for your integrations
Explore security controlsCompliance 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 guideImplementation
Technical reference
Review setup, record relationships, testing, and recovery for your implementation.
Authentication, permissions and API limits
Connection requirements and limits
MotherDuck
- Integration interface
- SQL through DuckDB clients and drivers using a MotherDuck (md:) connection
- Authentication
- Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults
- 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
- Generate a MotherDuck access token in Settings > General and enter it in the Stacksync connection form.
- Specify the intended database and schema and confirm read/write coverage for the selected tables.
Limitations to check
- Two-way sync is documented at connector level. Confirm table eligibility, writable columns, and the change-detection interval during setup.
Technical documentation
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
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.
Prepare MotherDuck 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.
MotherDuck setup checklist
- Generate a MotherDuck access token in Settings > General and enter it in the Stacksync connection form.
- Specify the intended database and schema and confirm read/write coverage for the selected tables.
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 MotherDuck and Zendesk planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.
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 MotherDuck (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.
- MotherDuck
- 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
Reporting dataset
Proposed company table in MotherDuck (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.
- MotherDuck
- 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 MotherDuck (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.
- MotherDuck
- 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 MotherDuck (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.
- MotherDuck
- 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 MotherDuck Proposed support case or ticket table in MotherDuck (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 MotherDuck 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 MotherDuck (choose its name) / Tickets, update direction, account tier, and related-record handling.
Custom API or workflow
- Best fit
- Consider when MotherDuck 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 MotherDuck / 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 MotherDuck (choose its name) or Tickets record needs a defined result in the other system.
- Start with MotherDuck Proposed support case or ticket table in MotherDuck (choose its name) and Zendesk Tickets. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve requester, organization, team, and status references before ticket updates.
- 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.
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 MotherDuck (choose its name) or Organizations record needs a defined result in the other system.
- Start with MotherDuck Proposed company table in MotherDuck (choose its name) and Zendesk Organizations. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve parent organizations, business units, and currency references before dependent transactions.
- 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.
Application user or identity 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 application user or identity table in MotherDuck (choose its name) or Users record needs a defined result in the other system.
- Start with MotherDuck Proposed application user or identity table in MotherDuck (choose its name) and Zendesk Users. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve tenant and group references and establish a protected administrative-account policy.
- 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 login, disabled account, missing group, and a user existing in two tenants.
If it fails: Review access impact before retrying a lifecycle change; reconcile current identity state and retain an approval trail.
Define an explicit handoff between MotherDuck and Zendesk
Validate the selected objects and operations even where connector-level direction is documented.
Starting event: A business event involving a selected business dataset needs a defined response involving Tickets or Users.
- Document what the source event means and which destination record or action should respond. A similar name does not establish a shared entity.
- Retain separate IDs and choose whether the destination is a report, a new work item, or a change to an existing record.
- 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 MotherDuck (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.
Proposed company table in MotherDuck (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 MotherDuck (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.
Proposed file or document metadata table in MotherDuck (choose its name) / 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.
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 MotherDuck Proposed support case or ticket table in MotherDuck (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 company change
Investigate
Inspect MotherDuck Proposed company table in MotherDuck (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.
Rejected or repeated application user or identity change
Investigate
Inspect MotherDuck Proposed application user or identity table in MotherDuck (choose its name) and Zendesk Users, their IDs, and the destination error.
Next action
Review access impact before retrying a lifecycle change; reconcile current identity state and retain an approval trail.
A record type or update is unavailable
Investigate
Check the MotherDuck 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 MotherDuck 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.
MotherDuck Zendesk 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 Zendesk. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Zendesk MotherDuck 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 MotherDuck. 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.
- Two-way sync is documented at connector level. Confirm table eligibility, writable columns, and the change-detection interval during setup.
FAQ
MotherDuck and Zendesk integration FAQ
-
Stacksync connects MotherDuck and Zendesk with two-way sync for supported records. Authorize the accounts, select the record types, and map compatible fields. Both connectors support reading and writing; object permissions determine the available fields. Use the Issues dashboard to inspect and resolve rejected updates.
-
Stacksync supports two-way sync between writable records in both systems. The chosen objects and fields must permit updates in both directions. Read-only fields can supply values but cannot receive updates. Stacksync can read database views; it does not write back to the view.
-
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Generate a MotherDuck access token in Settings > General and enter it in the Stacksync connection form. Provide the Zendesk subdomain in the Stacksync connection form and authorize the app. Use the pair worksheet to record ownership and acceptance criteria.
-
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
-
No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.
-
Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.
-
Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.
-
Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.
-
Start by reviewing Proposed support case or ticket table in MotherDuck (choose its name) in MotherDuck and Tickets in Zendesk. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.
-
Use MotherDuck Proposed support case or ticket table in MotherDuck (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.
Integration directory
Related integrations
Review documented support, sync direction, and setup requirements on each pair page. Search all 450 integrations listed for MotherDuck and Zendesk.
Popular · 6 of 450
-
MotherDuck and Orderful -
MotherDuck and ServiceNow -
Zendesk and ClickHouse -
Zendesk and Cloudera Data Platform -
Zendesk and Dremio -
Zendesk and Exasol
No integrations match .
Next step
See your workflow in Stacksync
Walk through your MotherDuck and Zendesk records, field mappings, and requirements with an integration engineer.
