Create a Trello App and Connect OOMOL
To connect Trello with OAuth2 in OOMOL, provide your own Trello app’s Client ID and Client Secret. You need an account that can create or manage apps in your Trello Workspace.
1. Create or open your Trello app
- Open Trello Apps Admin and sign in.
- Choose an existing app, or click New and fill in its name, Workspace, email, support email, and author. On your first visit, Trello may ask you to complete its Joint Development Agreement.
- For a new app used to connect OOMOL, choose My app doesn’t use Power-Up capabilities, then click Create.
- Open the app and choose OAuth 2.0 in the left navigation.
A Power-Up OAuth client restricts some permissions to one Workspace per authorization. Trello documents no such restriction for non-Power-Up OAuth clients. The Workspace selected when creating an app identifies its owner; the connected user’s permissions still determine which boards they can access.
2. Choose Confidential and add the callback URL
- Under Client Security Type, select Confidential. OOMOL exchanges and refreshes tokens on its backend using your client secret. A Public client has no client secret.
- Open OOMOL App Connections, find Trello, click Add account, and select OAuth2.
- Copy the full Redirect URI shown by OOMOL into Trello’s Callback URLs field. Click Add, then Save. Keep the URI unchanged, including its path and any trailing slash.
Trello requires at least one callback URL before OAuth 2.0 can be used.
3. Enable scopes and save credentials
In Trello’s Scopes table, enable the permissions requested by your OOMOL connection and click Save. The default connection requests these scopes:
read:board:trelloread:enterprise:trelloread:member:trelloread:organization:trellowrite:board:membership:trellowrite:board:trellowrite:enterprise:trellowrite:member:trellowrite:organization:membership:trellowrite:organization:trello
Board write scopes allow changes to cards, lists, comments, and board memberships. Workspace write scopes allow changes to workspaces and their memberships. The enterprise write scope allows enterprise management, and the member write scope covers actions such as starring boards or saving searches.
Request only the permissions you need. For read-only access, remove the write scopes under the advanced OAuth settings in OOMOL and enable the corresponding read scopes in Trello. OOMOL always includes read:member:trello to identify your account and offline_access to request refresh tokens. offline_access does not appear in Trello’s configuration table.
Copy the OAuth 2.0 Client ID and Client Secret into OOMOL’s OAuth client configuration and save. These are the credentials from the OAuth 2.0 tab, not the API key and token from Trello Auth.
4. Authorize and check access
Continue connecting in OOMOL and approve the request on Trello’s authorization page. After returning to OOMOL, list your Trello boards and check that a board you expect to access is present.
If authorization fails, check the exact callback URL, the Confidential security type, and the enabled scopes. If you cannot manage the app, ask a Workspace administrator for access. A connected account can access only resources permitted by Trello; using your own client does not grant additional board permissions.
If OAuth2 is unavailable in OOMOL, connect with a Trello API key and token. Creating an OAuth client does not automatically migrate that connection.
Official app creation guide and OAuth 2.0 client configuration.