Xero Setup
The superglue agent reads and writes Xero data through the Xero API, for example accounts, contacts, invoices, bills, credit notes, bank transactions, payments, manual journals, reports, tax rates, tracking categories and payroll. superglue has no managed Xero app, so the connection needs a Xero app with a client ID and a client secret. The agent can create this app for you in its own browser.
This guide walks you through the setup, which takes about ten minutes.
What to expect
Section titled “What to expect”- Runs as the signed-in user. All calls run as the Xero user who signs in. The agent can only see and change what that user can access.
- One organization per connection. After sign-in, the agent reads which organizations the connection can reach and saves the ID of the client’s organization as the
tenantIdsecret. When it finds more than one, it asks you which one the connection is for. - One app, many connections. After the first successful sign-in, superglue keeps the app as a sign-in app of your organization. Colleagues and later connections reuse it and only sign in.
- Approval before writes. The agent reads freely. In the default Ask for permission mode, it asks before it changes data.
What you need from the client
Section titled “What you need from the client”- A Xero user with access to the organization. The user signs in to Xero and approves the connection.
- Which organization. The live organization, or a separate organization for testing if the client has one. Use one connection for each organization.
- A Xero developer login for the app. You or the client create the Xero app. It can belong to your firm and serve all your clients.
Set up Xero
Section titled “Set up Xero”-
Ask the agent to connect Xero
- Start a session from the task, or click New session.
- Tell the agent what you need, for example: “Connect the client’s Xero organization.”
- If your organization has no Xero app in superglue yet, the agent asks whether you have the credentials. Pick Do it in the browser. The agent asks for permission to use the browser.
-
Let the agent create the Xero app
- The agent opens the Xero developer portal in its browser, in the side panel. Sign in yourself when the agent asks. If Xero asks for multi-factor authentication, complete it in the browser. You can open the browser in full screen to do this.
- The agent creates the app, adds the redirect URI, creates a client secret, and saves the client ID and the secret to the connection itself. You do not copy the values.
-
Sign in to Xero
- The agent shows a connection card. Click the sign-in button on the card.
- In the Xero sign-in window, sign in with the account that has access to the client’s organization, and approve the connection.
-
Test the connection
- Tell the agent: “List five contacts from Xero.” This request only reads data.
- If you get the contacts back, the connection works.
Create the app yourself
Section titled “Create the app yourself”Use this way when you cannot let the agent use the browser.
- In the Xero developer portal, create an app with the Web app integration type.
- Add the redirect URI. Copy the exact redirect URI from the connection card in superglue. On superglue Cloud, it is
https://app.superglue.cloud/api/auth/callback. - Create a client secret, and copy the client ID and the secret.
- Tell the agent that you have the credentials, and enter both values in the connection card. Do not paste them into the chat.
- Sign in to Xero on the card.
The sign-in requests these scopes by default:
offline_access, so that superglue can refresh the sign-inaccounting.invoices,accounting.payments,accounting.banktransactionsandaccounting.manualjournalsaccounting.contacts,accounting.settingsandaccounting.attachmentsaccounting.budgets.read,accounting.reports.aged.read,accounting.reports.balancesheet.read,accounting.reports.profitandloss.readandaccounting.reports.trialbalance.readpayroll.employees,payroll.payruns,payroll.payslip,payroll.timesheetsandpayroll.settings
To request fewer scopes, tell the agent which data the project needs before you sign in.
Limits
Section titled “Limits”- No managed app. Every superglue organization needs its own Xero app. After the first setup, it is reused.
- No separate sandbox connection. superglue has one Xero connection type. To test, connect a separate test organization.
- Scopes. If the app or the organization cannot grant a requested scope, the sign-in fails. Ask the agent to request only the scopes the work needs, and sign in again.
- Granular scopes only. Xero apps created on or after 2 March 2026 accept only granular scopes, such as
accounting.invoices. The olderaccounting.transactionsandaccounting.reports.readscopes fail for them. - Journals. The Xero Journals endpoint (
accounting.journals.read) needs Xero’s Advanced developer tier. superglue does not request it. - Connections and calls per app. A new Xero app is on Xero’s free Starter tier. It can connect 5 organizations and make 1,000 API calls a day for each organization. Paid tiers allow more organizations and 5,000 calls a day. The app owner changes the tier in the Xero developer portal.
Remove access
Section titled “Remove access”- In superglue, open Connections, open the menu of the Xero connection, and click Delete. This deletes the saved sign-in. It cannot be undone.
- To remove access on the client side, the client can disconnect the app in Xero. To stop all connections that use the app, delete the app in the Xero developer portal.
Do I need a new Xero app for each client?
Section titled “Do I need a new Xero app for each client?”No. One app can serve all your clients. Each client organization gets its own connection, and the user signs in to that organization.
How do I connect several organizations?
Section titled “How do I connect several organizations?”Add one connection for each organization, and put the organization in the connection name, for example “Northwind Xero”. Tell the agent which connection to use.
Does the agent change data during the test?
Section titled “Does the agent change data during the test?”No. The test lists contacts, which only reads data.