Trello

Overview
How to connect
Automated checks
Useful links

DSALTA connects to Trello using read-only API access to collect compliance evidence automatically. Data feeds into your Access accounts and Inventory pages.

Read-only access. DSALTA never modifies, creates, or deletes resources in your Trello environment.

DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.

What DSALTA reads

DSALTA reads the member list of every Trello workspace the connected account belongs to — names and usernames, which appears on your Access page. Trello’s members API exposes no email address, and it reports no per-member role or account status, so every member is listed as an active Member; and the boards that account is a member of, which appear on your Inventory page with their open/closed state. For the change-management checks it also reads that board’s labels and open cards.It calls these Trello endpoints:

/1/members/me
/1/members/me/organizations
/1/members/me/boards
/1/organizations/{organizationId}/members
/1/boards/{boardId}/labels
/1/boards/{boardId}/cards

Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Trello environment.

Troubleshooting

Integration shows Disconnected

There is no Reconnect button. Open Integrations → Connected, click Manage on the Trello card, and check the Status tab — it shows either Connected and working properly or Connection issues detected. To restore a broken connection you must Disconnect and connect again, which permanently deletes the data and tests collected from Trello. Trello tokens created this way do not expire, so this normally means the token was revoked in Trello, the Power-Up holding the API key was deleted, or the account that authorized DSALTA lost access to the workspace.

Data is not syncing

Verify the connected account still holds the permissions listed under Before you begin. Then open Integrations in the DSALTA sidebar, stay on the Connected tab, and click Sync from integrations at the top right. That button refreshes every connected integration at once — there is no per-integration sync control.

Trello REST API key and token. DSALTA only makes read (GET) calls to Trello — but note that the token the Power-Up page generates for you grants read and write access to your whole account unless you request scope=read yourself (see the note under Generate a Token).Before you begin

A Trello account (free plan works)
An API Key + Token from the Trello developer admin

You will need:

Field	Where to find it	Example
API Key	Open	—
Token	Open	—

Start in DSALTA

Open Integrations in the DSALTA sidebar, find Trello, and click Connect to open the connect panel. Leave it open — it lists every value you need, and you create those in the steps below.

Generate an API Key

Open trello.com/power-ups/admin, click New to create a Power-Up for any Workspace, open it, go to the API Key tab, and click Generate a new API Key. A free Trello account works; no paid or enterprise plan is required.

Trello Power-Ups admin page showing the Your Apps panel with a DSALTA Compliance Power-Up under Trello Workspace and the New button

Generate a Token

Next to the API Key, click the Token link and click Allow to generate a Token.

The Token link on the API key tab issues a token with read and write access that never expires — that is why the consent screen says “Make comments as you” and “until you disable it”. DSALTA only ever sends GET requests, so a read-only token is enough. To mint one, open this URL yourself with your API key pasted at the end: https://trello.com/1/authorize?expiration=never&scope=read&response_type=token&name=DSALTA%20Compliance&key=YOUR_API_KEY. Trello accepts scope=read, read,write or read,write,account, and expiration=1hour, 1day, 30days or never.

Use an account that belongs to the workspaces you want reviewed, and check which boards it is on. DSALTA reads members from every workspace this account belongs to, and boards only from the ones it is a member of — so a personal workspace shows up on the Access page, while a company board the account never joined is missing from Inventory.

Trello authorization page asking whether to give DSALTA Compliance access to the account, listing the logged-in user and the permissions the application will receive

Connect Trello

Paste the API Key and Token, then click Connect.Before the change-management checks can pass, the board you track changes on needs a label whose name contains “change” (for example change-request) — create it under Board menu → Labels. DSALTA treats every open card carrying that label as a change request, then verifies each has a member assigned and is closed within 30 days.

The change-management checks look at one board only. DSALTA evaluates the first open board Trello returns for the connected account, and every result records the name of the board it used. To get the board you track changes on evaluated, put the change-request label on it as well — any label whose name contains “change” counts — or archive the Trello boards you would rather DSALTA skipped. When the connected account can see no open board at all, these checks report an error reading “No Trello board in scope”.

Because Trello’s API never returns member email addresses, the two access checks match Trello usernames against your People page: first against a person’s username, then against the part of their email before the @. Members whose Trello username differs from both will stay unmatched on the Access page — enter their Trello handle in the Username field when you add the person on the People page (Add Person → Username). That field is offered while you create a person; the People detail sheet edits title, department and scope. For someone already on the page, give them an email whose local part is their Trello handle — the checks match on that too.

DSALTA validates the credential when you click Connect. On success the integration moves to the Connected tab, and Manage → Status reads Connected and working properly. Checks begin reporting after the first sync.

If the connection is rejected. Invalid API key or token.The on-screen message is generic — see Connection error messages.

Each check below re-runs once a day, at 02:00 America/New_York, while this integration is connected. Click any check for step-by-step remediation guidance.

Check	Severity	What it verifies
User access to Critical System should be valid	Info	Checks that members with access to Trello are authorized.
Offboarded users should not have active access	Info	Checks that offboarded employees no longer retain active Trello workspace access.
At least one change management system should be connected	Info	Checks that at least one change management system is connected.
Ticketing system for change management should be configured	Info	Checks that a ticketing system for change management is set up.
All change tickets should have an assignee	Info	Checks that all change management tickets have an assignee.
Change request tickets should be resolved within 30 days	Info	Checks that change request tickets are resolved within 30 days.

Topic	Link
Setup	Getting started with the Trello REST API
Setup	Trello REST API: Authorization
General	Trello website
DSALTA	Connection error messages

Getting Connected

Identity Providers

Cloud Infrastructure

Code Repositories

Security & Monitoring

Databases

SaaS & Productivity

What DSALTA reads

Troubleshooting

​What DSALTA reads

​Troubleshooting

What DSALTA reads

Troubleshooting