Xero automations
Finance · 12 integrations
Automating Xero typically means syncing invoices and contacts between your CRM or ecommerce store and your accounting records, triggering payment workflows, and keeping financial data consistent across tools without manual data entry. Businesses connect Xero to platforms like Salesforce, HubSpot, Shopify, and WooCommerce to eliminate double-entry and reduce reconciliation time. If you're evaluating automation platforms, the key variables are how each handles Xero's OAuth 2.0 requirements, webhook support, and a hard daily limit of 5,000 API calls per organization.
What it costs to automate Xero
Platform pricing at different volumes. Annual billing shown.
| Platform | Free tier | 100 tasks/mo | 1K tasks/mo | 10K tasks/mo |
|---|---|---|---|---|
| Zapier | 100 tasks/mo | Free | $69/mo | $69+/mo |
| Power Automate | 750 runs/mo | Free | $15/mo | $15/mo |
| Make | 1,000 credits/mo | Free | Free | $10.59/mo |
| Pipedream | 100 credits/mo | Free | $29/mo | $79/mo |
| n8n | Yes | $20/mo | $20/mo | $50/mo |
Xero integrations
Each page compares all five platforms for that pair.
Xero triggers & actions by platform
Which capabilities each platform supports for Xero.
| Capability | Zapier | Make | n8n | Power Automate | Pipedream |
|---|---|---|---|---|---|
| Triggers | |||||
| New Order | ✓ | — | — | ✓ | ✓ |
| Customer Created | ✓ | — | — | ✓ | — |
| Event Canceled | ✓ | — | — | — | ✓ |
| HTTP Webhook | — | ✓ | — | — | ✓ |
| Invitee Created | ✓ | — | — | — | ✓ |
| New Contact | ✓ | — | ✓ | — | — |
| New Invoice (Xero) | ✓ | — | — | — | ✓ |
| New Record | ✓ | — | ✓ | — | — |
| Order Created | ✓ | — | ✓ | — | — |
| Order Updated | ✓ | — | ✓ | — | — |
| New Deal | — | ✓ | — | — | — |
| Actions | |||||
| Create Contact | ✓ | ✓ | ✓ | ✓ | ✓ |
| Create Invoice | ✓ | ✓ | ✓ | ✓ | ✓ |
| Update Record | ✓ | ✓ | ✓ | ✓ | ✓ |
| Create invoice | ✓ | ✓ | ✓ | ✓ | — |
| Create Record | ✓ | ✓ | ✓ | — | ✓ |
| Create contact | — | ✓ | ✓ | ✓ | — |
| HTTP Request | — | ✓ | ✓ | — | ✓ |
| Update Contact | ✓ | ✓ | ✓ | — | — |
| Create a Record | ✓ | ✓ | — | — | — |
| Create Event | — | — | ✓ | — | ✓ |
Things to know about automating Xero
Daily API Call Ceiling
Xero enforces a hard limit of 5,000 API calls per day per connected organization, dropping to just 1,000 on the Starter tier. Syncing a single invoice typically consumes 5–6 API calls, so unoptimized integrations can exhaust this budget with fewer than 900 invoices before midnight.
Batch to Stretch Limits
The Xero API allows up to 50 invoice elements per POST or PUT request, meaning you can sync 800 invoices using only 20 API calls instead of 4,000+. Any automation platform — Zapier, Make, n8n, Power Automate, or Pipedream — that sends one record per request will burn through your daily quota far faster than one using batched payloads.
Webhook Reliability Requirements
Xero webhooks require your endpoint to respond with HTTP 200 within 5 seconds and validate every request using HMAC-SHA256 signature verification — failure to comply results in subscription suspension. Real-time triggers via webhooks reduce API traffic by more than 60% compared to polling, making them critical for staying inside rate limits at any meaningful transaction volume.
OAuth Token Expiry Risk
Xero access tokens expire after 30 minutes and refresh tokens expire after 60 days of inactivity — if your automation goes dormant for two months, users must fully reauthorize. Scope configuration errors are another common failure point, with misconfigured callback URLs or mismatched scopes responsible for the majority of OAuth authentication failures across all platforms.
n8n Node Coverage Gap
The native n8n Xero node covers only Contacts and Invoices, leaving out Bank Transactions, Manual Journals, Bills, and most other endpoints. Accessing the full API in n8n requires the generic HTTP Request node with manually configured OAuth2 credentials, including authorization URLs, token URLs, and scopes set up through the Xero Developer Portal.
Recent Deprecations to Check
The Accounting Activities API was decommissioned on April 6, 2026 — any integration using Account Usage, Lock History, or User Activities endpoints will now return errors. The ExpenseClaims endpoint was also disabled in February 2026 and the Employees endpoint deprecated in early 2026, so existing automations built on these should be audited and replaced before they fail silently.
What breaks at scale
At unoptimized rates of 5–6 API calls per invoice, an integration syncing 800+ invoices per day will exhaust Xero's 5,000 daily API call limit before all records are processed — and if you're on the Starter tier, that ceiling is only 1,000 calls total. What makes this painful is that Xero returns a 429 error and your automation stalls mid-batch with no automatic retry in many platform configurations, meaning some invoices simply never sync without an alert firing. Polling-based automations on Zapier, Make, or Power Automate that check Xero every few minutes compound this by burning through the 60 calls-per-minute limit long before touching your actual business logic.
Xero refresh tokens expire after 60 days of non-use, and if your automation runs infrequently — seasonal businesses, quarterly reporting workflows, or anything paused for maintenance — you will return to a silently broken connection that requires full user reauthorization. This affects all five platforms (Zapier, Make, n8n, Power Automate, Pipedream), but is especially sharp in n8n self-hosted environments where there is no automated token health monitoring. Long-running jobs that hit the 30-minute access token expiry mid-execution will also fail partway through without proper refresh logic built in, potentially leaving records in a half-synced state.
Each connected Xero organization gets its own independent 5,000 daily API call quota, but the rate limit is per connection — not pooled — so an automation serving 10 client organizations cannot redistribute unused quota from one to cover another that is spiking. The March 2026 pricing change introduced egress fees of $2.40 AUD per GB across all tenancies, meaning high-volume data pulls for reporting or analytics across multiple organizations can generate unexpected infrastructure costs that scale non-linearly. Developers building multi-tenant tools on top of Xero have reported annual cost increases from near-zero to over $17,000 AUD under the new tiered model.
Frequently asked questions
Which automation platform works best with Xero — Zapier, Make, n8n, Power Automate, or Pipedream?
Zapier offers the most accessible out-of-the-box Xero integration with native support for line items, but requires Standard or Advisor-level Xero account permissions and has a 7-day lookback limitation on the New Payment trigger. Make and Pipedream give you more control over batching and request logic, which matters when working near Xero's 5,000 daily API call limit. n8n's native node is limited to Contacts and Invoices, while Power Automate's Xero connector coverage varies — for either platform, complex workflows often require falling back to raw HTTP requests against the Xero API.
What are Xero's API rate limits for automations?
Xero allows 60 API calls per minute and 5,000 per day per connected organization, with a concurrent limit of 5 simultaneous calls — the Starter tier is capped at just 1,000 daily calls. Exceeding these limits returns a 429 Too Many Requests error, and your automation must pause before retrying. Batching up to 50 records per request and using webhook-based triggers instead of polling are the two most effective ways to stay within limits on any platform, including Zapier, Make, n8n, Power Automate, and Pipedream.
Does Xero support webhooks for real-time automation triggers?
Yes, Xero provides webhooks for events including invoice updates, contact changes, and payment notifications, with a newer per-event schema model introduced in late 2025 starting with Credit Notes. Setting them up requires registering an app in the Xero Developer Portal and exposing a publicly accessible HTTPS endpoint that responds within 5 seconds with a valid HMAC-SHA256 signature validation — missing that window causes subscription suspension. Platforms like Pipedream and n8n (via HTTP trigger nodes) can receive these directly, while Zapier and Make handle Xero events through their own polling or native trigger mechanisms.
How do I connect Xero to my CRM or ecommerce platform for automated invoicing?
Connecting Xero to CRMs like Salesforce, HubSpot, Pipedrive, Apollo, or Attio — or ecommerce platforms like Shopify and WooCommerce — is a common use case handled by Zapier, Make, n8n, Power Automate, and Pipedream. The integration maps new deals or orders to Xero invoices or contacts, typically using the accounting.transactions and accounting.contacts OAuth 2.0 scopes. The main practical limits are Xero's 5,000 daily API calls per organization and the need for Standard or Advisor account permissions on the Xero side for platforms like Zapier to authenticate successfully.