Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 06:00 UTC
| 1 | ## How do I set up custom OAuth credentials for Xero? |
| 2 | |
| 3 | Composio has no managed OAuth app for Xero, so you need your own Xero app. It also lets you control the app name users see and the permissions your integration requests. |
| 4 | |
| 5 | ### Create the Xero app |
| 6 | |
| 7 | 1. Sign in to the [Xero Developer Portal](https://developer.xero.com/app/manage), open your apps, and click **New app**. |
| 8 | |
| 9 |  |
| 10 | 2. Enter an **App name** and **Company or application URL**, and select the **Auth code** flow for a web app. |
| 11 | |
| 12 |  |
| 13 | 3. Set the **Redirect URI** to `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field in your Composio auth config. Fill in the remaining required fields and click **Create app**. |
| 14 | 4. Open the app's configuration and copy the **Client ID**. Click **Generate a secret** and copy the **Client Secret**. |
| 15 | |
| 16 | ### Create the auth config in Composio |
| 17 | |
| 18 | 1. In the Composio dashboard, go to **Auth Configs**, click **Create**, and select **Xero**. |
| 19 | |
| 20 |  |
| 21 | |
| 22 |  |
| 23 | 2. Choose **Your Own Credentials** and paste the **Client id** and **Client secret**. |
| 24 | |
| 25 |  |
| 26 | 3. Keep the default scopes or adjust them (see below), then click **Create Auth Config**. |
| 27 | 4. Click **Connect Account**, sign in to Xero, check the app name, organisation, and permissions, and click **Allow access**. |
| 28 | |
| 29 |  |
| 30 | |
| 31 |  |
| 32 | 5. Open **Accounts** and confirm the connected account shows as **Active**. The auth config's **Enabled** label alone doesn't confirm a connection. |
| 33 | |
| 34 |  |
| 35 | |
| 36 | See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow. |
| 37 | |
| 38 | ### Scopes |
| 39 | |
| 40 | The default auth config requests `openid`, `profile`, `email`, `offline_access`, plus read and write access to accounting, files, and projects (for example `accounting.invoices`, `accounting.contacts`, `accounting.payments`, and the `accounting.reports.*.read` scopes). Keep `offline_access` so Composio can refresh tokens without another sign-in, and remove any accounting areas your tools don't use. |