After this article
You’ll be able to connect Trello to Lumos to sync users, organization and board memberships, and roles, provision users and role assignments, and resolve common connection issues.Capabilities
Provisioning and deprovisioning require an Administrator, Owner, or equivalent admin role in Trello.
On connections without Is Enterprise Instance? turned on, Deactivate and Delete may not complete right now. If you need to deprovision a Trello user on one of these connections, contact support@lumos.com.
Activity Tracking
Status: Supported. The Trello connector tracks user last login events.Required plan and roles
- Trello role: provisioning and deprovisioning require an Administrator, Owner, or equivalent admin role. Standard users can’t perform these actions even when the OAuth scopes or API keys are correct.
- Trello plan: sync works on all Trello plans. Creating user accounts and SCIM-based provisioning require Trello Enterprise.
- OAuth scopes: Lumos requests all three scopes below when you authorize the connection:
- SCIM Token: needed only to enable SCIM-based user provisioning on Enterprise. Leave it empty if you don’t need SCIM-based user provisioning.
Read-only access vs provisioning
Is read-only possible? Not at the token level. Lumos always requests theread, write, and account scopes when you authorize the Power-Up, and Trello Power-Up API keys don’t carry scopes of their own, so every connection’s token can write. SCIM-based user provisioning also needs Is Enterprise Instance? turned on and a SCIM Token, but organization and board role changes use the authorized token either way.
What read-only requires. There’s no separate read-only setup. Connect with your Power-Up’s API key and secret as described below. Lumos syncs with the same authorization it would use to provision.
What full provisioning requires. The same Power-Up’s API key and secret, plus an Administrator, Owner, or equivalent admin role in Trello to actually run provisioning and deprovisioning actions. Creating or SCIM-provisioning user accounts additionally requires the Trello Enterprise plan, and SCIM-based provisioning also requires a SCIM Token.
Watch out for. Board, Enterprise, and Org role assignments can provision on any plan, but creating or SCIM-provisioning user accounts only works on Enterprise. Because Lumos always requests the write scope, regenerating the Power-Up key doesn’t make a connection read-only.
Instructions
Each customer creates their own Trello Power-Up, not a shared Lumos app, so you supply that Power-Up’s API key and secret. Phase 1: Create the Trello Power-Up (OAuth app)- Go to
https://trello.com/power-ups/adminand click New to create an integration. - Fill in the integration name, workspace, email, support info, and company name.
- Under Allowed Origins, add the Lumos callback URL
https://app.lumosidentity.com. This is required. Without it Trello rejects the OAuth authorization with “Invalid return_url”. - Click Create, then generate a new API key (or import an existing one). You don’t choose scopes here; Lumos requests them when you authorize the connection in Phase 2.
- Go to Settings > Integrations and open the Trello card (reconnect an existing card or add a new one).
- Copy the Power-Up’s API Key into Client ID and its Secret into Client Secret.
- Tenant Name: the workspace slug of the parent organization or enterprise that owns the boards. For
https://trello.com/w/slytherin/homethe tenant name isslytherin. - Toggle Is Enterprise Instance? on if your Trello account is an Enterprise instance. Enterprise accounts have extra administrative capabilities and use different API endpoints for user management.
- SCIM Token: to enable SCIM-based user provisioning (Enterprise only), log in to Trello as an admin of your enterprise and get the token at
https://trello.com/enterprise/<your enterprise name>/token. Leave it empty if you don’t need SCIM-based user provisioning. - Click Connect, and authorize the Power-Up when Trello prompts you.
API Endpoints Used
Troubleshooting
Connecting fails with “Invalid return_url. The return URL should match the application’s allowed origins.” The Lumos callback URL isn’t registered on your Power-Up. In the Trello Power-Up admin, addhttps://app.lumosidentity.com under Allowed Origins, save, and retry the connection. This is separate from the “OAuth state not returned / page spinning” issue.
Invalid API Key or Token error. Verify the Client ID and Client Secret were copied without extra spaces and match the API Key and Secret on your Power-Up, and make sure Tenant Name points at the correct workspace or organization. If you reconnect, authorize the Power-Up again when Trello prompts you.
Insufficient Permissions error. Confirm you’re a member of the organization you’re syncing, that you have visibility permissions for the boards, and that the token was authorized with read access. Contact your Trello workspace admin if the permissions look wrong.
Members not syncing correctly. Check that members have confirmed their Trello accounts and are active in the workspace, review the sync logs, confirm the API credentials have organization read access, and look for deactivated or pending member invitations.