A Service for Managing Connections Between Trello and Work Tools

Connection permissions can now be split into smaller parts

Trello officially launched a new account connection model on September 15, 2026. OAuth 2.0 lets an external app act in Trello only within the scope a user approves, without receiving the user’s password. It suits CRM, scheduling, reporting, and notification services where a person logs in and gives consent.

Previously, apps often received broad permissions such as reading and writing at once. Under the new model, requests can be separated into scopes such as reading boards, editing cards, managing board members, and viewing workspace information. The consent screen has also changed to show which data an app will access.

The temporary access token an app uses to connect to Trello is valid for one hour by default. The refresh token used to obtain another access token is valid for 90 days by default and is replaced with a new token after one use. The structure is designed to check that a connection remains valid, rather than leaving a one-time permission in place indefinitely.

Power-Ups, extensions that run inside Trello, can have board- and workspace-related permissions limited to one workspace. But Power-Ups always have board read and write permissions enabled. A service that needs read-only access should first consider whether it is better connected as a standard app.

The existing connection model remains supported, with no end date set. The older approach may be a better fit for bots that do not involve a person logging in or for automated jobs that run on their own overnight. This is not a change that requires everyone to rebuild immediately. It creates an option to show customers more clearly what permissions they are granting.

Work stops between tools

Consider the operations manager at a window-and-door installation company with 12 employees. Customer inquiries enter a CRM tool, work for each site becomes a Trello card, visit schedules are recorded in a separate calendar, and weekly reports are written in a document.

For every inquiry, the operations manager copies the customer’s name and address into Trello, then enters the confirmed visit date into the calendar again. When an assignee completes a card, the manager transfers the construction status to the CRM tool. On Friday, the manager counts cards and reasons for delays, then pastes them into the report. One job moves through four tools, with the same information copied by hand several times.

Connections also fail in different ways. When a token expires, only automated notifications may stop. When a new feature requires additional permissions, existing users may need to consent again. The operations manager may not be able to tell immediately whether notifications stopped because there was no work or because the connection broke.

With the new model, the first step can separately explain, “Read boards and cards in the selected workspace,” and, “Update the status of completed cards.” If member management is not needed, that permission is not requested. Users can understand what they are granting before they connect, while the service operator can record the scope allowed by each customer.

The service can then show connection status alongside the work flow. For example: “Inquiry transfer from CRM to Trello is working,” “Visit-date transfer from Trello to the scheduling tool needs reconnection,” and “Four cards were not transferred because this connection stopped.” Instead of opening all four tools one by one, the operations manager can log in again directly at the point where the flow broke.

Building a connection service does not remove every permission issue. Some cases, such as Power-Ups, require read and write access together. Customers that use several workspaces may need to connect each one. If the platform requires more access than the customer intends to grant, say so clearly before the connection button.

Some work remains in human hands. Deciding whether a site photo requires rework, negotiating a schedule with a customer, and explaining a delay cannot simply be passed to automation. A good connection service does not eliminate human judgment. It reduces time spent copying and checking, and shows where work stopped between tools.

Connection itself is sold as a service abroad

Nango, a US company, provides consent screens, token storage, token refresh, and connection-status management for product teams that want to connect accounts with other work tools. It charges based on the number of connected external accounts, execution time, and the volume of data processed. The business saves each product team from building login and reconnection features from scratch for every tool.

Motion, a work-automation product, began by assigning its account-connection layer to Nango. According to a case study published by Nango, Motion released its first workflow-building feature in about three to four months and later expanded to about 189 connectable services. The figures come from the vendor and need independent verification, but they show that connection management can be sold as a distinct product.

Paragon, a US company, helps customers connect sales, customer-support, and conversation tools inside their own products. It charges based on Connected Users, defined as the number of unique user IDs belonging to customers connected to one or more integrations, with specific pricing provided after consultation. It provides synchronization and webhook features as well as connection screens.

Appsmith, which builds internal work tools, rebuilt its external-service connection capability around Paragon. According to Paragon’s own case study, the time to launch one new connection fell to under a day, 15 connection features were deployed, and customer implementation time fell by 80%. This is also a vendor claim, but it highlights that building connections between tools can take more time than building the screens where users work.

Four ways to start small

1. A broken-connection dashboard

• A service that shows the connection status of Trello, CRM, scheduling, and reporting tools in one place, and finds work that has stopped moving.
• It is for operations teams at installation companies with around 10 employees that manage site work in Trello boards while recording customer inquiries and visit schedules in other tools.
• The one-hour access-token and 90-day refresh-token structure makes ongoing connection health more important than the initial connection alone.
• The first screen shows working and reconnection-needed status for each connection, the number of cards not transferred, and the last time it worked normally.

2. A Korean-language permission explanation screen

• A service that creates a plain-Korean explanation of requested permissions and why they are needed before a user clicks the Trello connection button.
• It can be embedded by operators of Korean business services that read Trello cards to create quotes or weekly reports.
• Since permissions can be separated into board reading, card editing, member management, and more, the explanation can make a meaningful difference even for the same connection.
• The first screen places “What we view,” “What we change,” and “Permissions we do not request” side by side.

3. Find work copied by hand

• A service that follows work from a customer inquiry to a Trello card, a visit schedule, and a completion report, recording where someone re-enters information.
• It is for dispatch coordinators at cleaning and repair companies that receive online inquiries, create work in Trello, and schedule technicians in a calendar.
• Because connection permissions can be divided by the task required, the service can remove one copy-and-paste step without automating the entire operation.
• The first screen lists, in time order, fields entered repeatedly across tools today and work that has not yet moved to the next tool.

4. A handover inbox for departing staff and contractors

• A service that shows who connected which external service to which workspace and board, and helps hand over those connections when responsibility changes.
• It is for small advertising agencies that operate separate Trello workspaces for each client and frequently change freelance planners and producers.
• Workspace-level limits and granular permissions make it possible to organize around the connected work scope rather than an entire account.
• The first screen shows each person’s connections, approved actions, last-use date, and items to hand over to the new owner.

What to check in 30 minutes today

Ask one team that uses Trello alongside other tools to share its screen and show, in order, where each piece of information goes from one customer inquiry to completed work. If the team moves through three or more tools, copies the same information at least twice, or does not know which screen to check when a connection fails, a small connection-status dashboard is worth testing first.

Why this matters where you are

Check whether teams in your market copy the same customer or job information across a task board, a CRM tool, a calendar, and a report. The tools and permission rules may differ, but the practical question is the same: can people see where work stopped and reconnect only the access required? Start by observing one complete job flow before trying to automate it.