Zapier, Slack and Xero without code

Not everything needs an engineer. The Connections page in the Xace web app has pre-built integrations that cover the most common needs. This page tells you what each does and points you at the setup articles.

Zapier

Connects Xace to thousands of apps with no code. Under Connections, API & Webhooks, accept the Zapier invite, then build Zaps that trigger on Xace events or read Xace data.

• Triggers come from webhook events: PaymentRequested, PaymentApproved, PaymentDeclined, TransactionCreated, TransactionConfirmed, TransactionReceived, PayeeCreated and more.
• Reads cover accounts, transactions, payees, approvals and statements.
• Writes can create payments.

Good for: "when a payment is requested, create a task in Jira", "when money is received, add a row to a sheet", "when a payment is declined, email the requester".

Setup: Zapier integration.

Slack

Sends account and payment activity into Slack channels in real time. You map each Xace account to a channel and choose which events to send. Notifications include amount, currency, payee, account, status and a link back to the item in Xace.

Good for: an approvals channel where pending requests appear with a link, a treasury channel for large inbound payments, a private channel for sensitive activity.

Setup: Slack integration.

Xero and QuickBooks

Map each Xace account to a ledger account, review transactions with GL codes and descriptions, and sync. Covers incoming and outgoing payments, fees, FX movements and card transactions. Ask support to enable it.

Good for: any finance team on Xero or QuickBooks. This replaces CSV exports entirely.

Setup: Xero integration.

Jira and Trello

Create and update tasks from account activity for teams that run operations out of a project tool.

Setup: Jira integration, Trello integration.

When to use the API instead

• You need data in your own system, not a SaaS tool.
• You are creating payments programmatically at volume, where idempotency and error handling matter.
• You need the full transaction record, or daily CAMT.053 statements for reconciliation.
• You need to react to events in your own code rather than in Zapier.

For the decision in more detail, see Choosing between the API, webhooks, Zapier and Open Banking.