Skip to content

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

New

Stacksync MCP is here. Give Claude, Cursor, and any MCP client governed access to your syncs, workflows, and connections.

Set up MCP
Accounting and finance / Business productivity · Two-way sync platform

Rillet and Zendesk integration — two-way sync

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

Set this up from Claude or ChatGPT
  • Field mappings and sync direction under your control
  • Inspect and resolve record errors in one dashboard
Two-way sync for supported objects
stacksync.com
Rillet
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

Customer sync test

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

Starting eventA change involving Rillet Customer or Zendesk Organizations needs a defined result in the other system.

  1. Start with Rillet Customer and Zendesk Organizations. Use the record-matching and field-ownership rules from your mapping worksheet.

  2. Resolve person or company type, legal entity, business role, and any billing account before transactions.

  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 an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

Review records and field ownership

AI assistant

Set up Rillet and Zendesk from Claude or ChatGPT

Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste.

1. Add the Stacksync MCP server

Server URL

https://mcp.stacksync.com/mcp

In Claude

  1. Open Customize → Connectors, select + Add, then Add custom connector.
  2. Name it Stacksync and enter https://mcp.stacksync.com/mcp.
  3. Select Connect, sign in to Stacksync and choose your workspace.

In ChatGPT

  1. Open Settings → Apps → Advanced settings and turn on Developer mode.
  2. Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth.
  3. Sign in to Stacksync, then enable Stacksync from the tools menu in a chat.
Set up Codex or Claude Code

Codex

codex mcp add stacksync --url https://mcp.stacksync.com/mcp
codex mcp login stacksync

Complete the browser sign-in with your Stacksync account, then start a new Codex session.

Claude Code

claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp

Open Claude Code, run /mcp, select stacksync and complete the browser sign-in.

Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet.

Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: setup steps in the docs.

2. Ask your assistant

Create a two-way sync between my Rillet and Zendesk.

Also from the same chat

You can also ask for workflows and AI agents (Genies) that use Rillet and Zendesk. The assistant checks what each app supports, for example:

  • “Build a workflow that messages our team in Slack when a Rillet record changes.”
  • “Create a Genie that answers questions about our Zendesk data in Slack.”

What happens next

  • Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat.
  • Gives you a secure sign-in link for each app it connects; you open it and sign in to that app.
  • Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first.

New to Stacksync? Create an account first, then sign in from your assistant.

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 Rillet and Zendesk
Rillet recordZendesk recordRecord matchingField ownership
CustomerDocumented record: Incremental: Yes; historical: Yes; delete detection: YesCustomer identity assessmentOrganizationsDocumented record: :clock1: On requestDetermine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.

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 Rillet and Zendesk

Put your Rillet 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 Rillet and Zendesk workflow to test, define what success looks like, and decide who handles failed updates.

  • Keep customers and invoices aligned between Rillet and a CRM so finance and sales work from the same account records.

  • Mirror journal entries and contract revenue data into a warehouse for board and ARR reporting.

  • 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.

Rillet

Read and write support varies by record

Record types covered in the setup guide

Record typesCoverage and requirements
  • Customer
  • Invoice
  • Vendor
  • Credit Memo
  • Bill
  • Journal Entry
  • Invoice Payment
  • Charge
  • Reimbursement
  • Custom Field
Incremental: Yes; historical: Yes; delete detection: Yes. Confirm field permissions and sync direction.
  • Account
Incremental: Yes; historical: Yes; delete detection: Yes, every 1h. Confirm field permissions and sync direction.
  • Subsidiary
  • Tax Rate
  • Product
  • Contract
  • Bank Account
Incremental: No; historical: Yes; delete detection: Yes, every 1h. Confirm field permissions and sync direction.
  • Bank Transaction
Incremental: No; historical: Yes; delete detection: Yes, every 4h. Confirm field permissions and sync direction.

Read the Rillet 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 requirementRilletZendesk
Integration interfaceREST API (OpenAPI-specified, with production and sandbox environments)REST API
AuthenticationAPI key generated in RilletOAuth app authorization
Change detectionHistorical and incremental syncs are documented by object.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

Rillet
Integration interface
REST API (OpenAPI-specified, with production and sandbox environments)
Authentication
API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only to enable writes for two-way sync; check Read Only to prevent write-back
Change detection
Historical and incremental syncs are documented by object. Some objects have only historical sync; delete detection intervals vary.
Read access
Available for supported records
Write access
Available for supported records
Setup requirements
  • Generate an API key in Rillet Organization Setting > API Access.
  • For two-way sync, clear the Read Only setting; use a read-only key when the integration only needs outbound data.
Limitations to check
  • Some objects have historical sync only; deletion checks for supported objects can run at different intervals.
Technical documentation

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

Rillet 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 Rillet 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.

Rillet setup checklist
  • Generate an API key in Rillet Organization Setting > API Access.
  • For two-way sync, clear the Read Only setting; use a read-only key when the integration only needs outbound data.

Setup guides: Authorize Rillet Connection

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 Rillet 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

Customer identity

Customer / Organizations

Before linking Rillet Customer to Zendesk Organizations, check whether the customer is an individual or a company. Match the correct record type in each system.

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

Rillet
Documented record · Incremental: Yes; historical: Yes; delete detection: Yes
Zendesk
Documented record · :clock1: On request
Record identity
Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.
Field ownership
Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.

Fields to include

  • Source customer ID
  • Person/company classification
  • Legal entity or business unit
  • Destination identity reference
Record dependencies
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Validation
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Recovery
Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

References: Rillet: Customer documentationZendesk: Organizations documentation

Compare integration approaches

Use Rillet Customer and Zendesk Organizations 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: Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. 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 Rillet 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 Customer / Organizations, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit
Consider when Rillet 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. Separate reading history from actions that send messages, grant access, or post transactions.

File or scheduled snapshot

Best fit
Consider for a one-time Rillet / 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

Customer 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 Customer or Organizations record needs a defined result in the other system.

  1. Start with Rillet Customer and Zendesk Organizations. Use the record-matching and field-ownership rules from your mapping worksheet.
  2. Resolve person or company type, legal entity, business role, and any billing account before 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: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Reconcile Rillet business records with Zendesk

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

Starting event: A finance-owned record in Rillet needs operational visibility through Tickets or Users.

  1. Select Customer or Vendor with the correct legal entity, period, and currency.
  2. Define a reporting relationship in Zendesk; do not equate customer records, ledger accounts, and posted transactions.
  3. Decide whether the process only reports a financial state or requests an approved accounting action, and maintain a separate transaction ID for each action.

Expected result: Totals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.

If it fails: Verify posting and settlement state before retrying. Use the approved adjustment path for already-posted transactions.

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.

Customer / Organizations

Test case

Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

Expected result

The expected customer 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 customer change

Investigate

Inspect Rillet Customer and Zendesk Organizations, their IDs, and the destination error.

Next action

Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

A record type or update is unavailable

Investigate

Check the Rillet 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 Rillet 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.

Rillet Zendesk Timing depends on the connected systems

Detect changesHistorical and incremental syncs are documented by object. Some objects have only historical sync; delete detection intervals vary.

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

Zendesk Rillet 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 Rillet. 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.
  • Some objects have historical sync only; deletion checks for supported objects can run at different intervals.
FAQ

Rillet and Zendesk integration FAQ

Further reading

Guides and resources

Next step

See your workflow in Stacksync

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

See Stacksync in action Explore plans and pricing