Xero and Zendesk integration

What moves between them

Xero contacts flow into Zendesk as organizations, creating or updating the customer record in the support system. Invoice records flow from Xero into Zendesk ticket custom fields or organization metadata, tagged with invoice status and due date so support agents see financial context without leaving Zendesk. Payment status flows from Xero's payment records back to Zendesk ticket fields. The sync runs on a schedule tied to your billing cycle or can be triggered by Xero webhook events. Updates to contact information in Xero trigger updates in Zendesk; disputes or overdue flags in Xero can trigger Zendesk automations to escalate or re-assign tickets.

How ml-connector handles it

ml-connector stores both Xero OAuth credentials and Zendesk authentication (OAuth or API token) encrypted. On the Xero side, it manages token refresh every 30 minutes and respects the rate limit of 60 calls per minute per tenant by queueing requests and applying backoff. Contacts are fetched from Xero and mapped to Zendesk organizations by matching email domains or explicit contact-to-organization fields. Invoices are fetched using Xero's If-Modified-Since header for delta sync, then written to Zendesk ticket custom fields or organization metadata. Zendesk webhook signature verification is performed on all inbound events using HMAC-SHA256. The integration is read-heavy; Xero remains the system of record for financial data, and Zendesk tickets are never written back to Xero's GL accounts or payment records. If a Zendesk webhook delivery fails, ml-connector retries with exponential backoff, and every record carries an audit trail so disputes can be resolved.

A real-world example

A small to mid-sized professional services firm runs Xero for invoicing and accounting, and uses Zendesk for customer support. When a customer contacts support, agents see the customer's outstanding invoices and payment history in the ticket record without leaving Zendesk. The finance team can reference support conversations when customers dispute charges, since tickets link to the invoice records in Xero. Before the integration, agents had to log into Xero to look up invoice details, and support notes were siloed from accounting notes. With Xero and Zendesk connected, the entire customer picture is visible in Zendesk, and the finance team can review Zendesk comments when reconciling accounts or chasing payment.

What you can do

• •Sync Xero contacts into Zendesk organizations, keeping customer records aligned across both systems.
• •Map Xero invoice records to Zendesk ticket custom fields or organization metadata so agents see payment history and outstanding balances.
• •Reflect Xero payment status and due dates in Zendesk organization records for financial context in every support interaction.
• •Manage Xero OAuth2 token refresh, rate limit compliance, and Zendesk webhook signature verification automatically.
• •Maintain a full audit trail on every contact and invoice record, with error replay if a sync fails.

Questions

Can Zendesk sync payment or invoice changes back to Xero?

No. Zendesk has no native invoicing or GL accounting entities, so Xero remains the system of record for all financial data. ml-connector moves contacts and invoice information into Zendesk one direction only, so agents see financial context without the ability to create or modify invoices in Zendesk.

What happens if an invoice is updated in Xero after a Zendesk ticket is created?

ml-connector uses Xero's If-Modified-Since header to poll for invoice changes and updates the corresponding Zendesk ticket custom fields when a change is detected. The sync runs on a configurable schedule so updates flow within minutes, and the audit trail records every change.

How does ml-connector handle Zendesk webhook authentication?

ml-connector verifies every Zendesk webhook signature using HMAC-SHA256 with the shared signing key, rejecting any unsigned or tampered events. If a webhook delivery fails, ml-connector retries with exponential backoff and logs the failure to the audit trail.