> ## Documentation Index
> Fetch the complete documentation index at: https://docs.connie.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Xero

> Use your connected Xero accounting account in AI Chat and Workflows.

Connect **Xero** from Tools, then select that account in AI Chat or a Workflow action. Review the Xero consent screen and choose the organisations you want to connect. If an existing connection lacks a permission required by an action, reconnect it and grant that permission.

Start with **List Xero Tenants** (or **Get Xero Tenants**). Each result includes `tenantId` and `tenantName`. Use the intended organisation's `tenantId` in subsequent actions on that same connected account. Selecting an account alone does not select an organisation.

For example, ask: “List the Xero organisations connected to my accounting account, then show the authorised invoices for Example Ltd.” Connie can list tenants, select the matching organisation, and list invoices using `where: Status=="AUTHORISED"`.

| Resource | Actions |
| - | - |
| Organisations (tenants) | List, get the connected tenant list |
| Accounts, bank transactions, contacts, credit notes, invoices, items, purchase orders | List, get, create, update |
| Payments | List, get, create |

These are the 33 actions documented in the [Nango Xero integration guide](https://nango.dev/docs/api-integrations/xero). Background syncs from that guide are separate and are not Workflow actions.

In a Workflow, choose the Xero action and account, enter or map **Tenant ID**, and map any resource ID from an earlier list/get result. Create and update actions accept one **Payload** JSON object using Xero API field names. Additional documented fields are preserved. For example, create an invoice with:

```json theme={null}
{
  "Type": "ACCREC",
  "Contact": { "ContactID": "the-contact-uuid-from-xero" },
  "LineItems": [{ "Description": "Consulting", "Quantity": 1, "UnitAmount": 125, "AccountCode": "200" }]
}
```

Use a real contact UUID and a valid account code for your organisation. Amounts use decimal currency units. A payment action records an accounting payment against an invoice or credit note; it does not initiate a bank transfer. Create/update actions do not email documents. Archiving, deleting and voiding through these payloads are unsupported and rejected.

Results have a `data` array containing Xero records, with provider IDs available for downstream variables. Paginated lists return one page of up to 100 records and `nextPage`. A non-null `nextPage` suggests the next page to request; a final full page may be followed by an empty page. Accounts, items and tenants use Xero's unpaginated endpoints.

Each action costs **1 Connie credit**. Xero subscriptions and provider limits are separate. Your workspace's tool permissions and connected-account access still apply.

When the caller supplies a stable invocation identity, retries of the same final request reuse an account- and organisation-scoped idempotency key. Different request contents or targets receive different keys. Older callers without that identity remain supported without a provider retry key. If a timeout leaves the outcome uncertain, inspect Xero before starting a new request. A validation error is a failed action; correct fields, tax/account codes or document status before retrying. Reconnect expired or revoked accounts, and wait for the provider's retry window after rate limits.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.