Trello support

Last updated date:

Connect, reconnect, and troubleshoot Trello without sharing credentials or customer content through support channels.

1. Before you start

  • Create a Trello Power-Up/API key and user token from a dedicated account.
  • Grant read and, only when identity verification requires it, account access.
  • Collect workspace and board IDs when the connection should not read every visible board.
  • Do not send Trello credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
Trello authorizationTrello's REST API authorization guidance.

2. Connect Trello

  1. In Seedling, open Connections and choose Trello.
  2. Connect from workspace scope as a current Seedling workspace administrator.
  3. Enter the API key, user token, optional account label, workspace IDs, and board IDs; Seedling always calls the Trello API.
  4. Seedling verifies the token owner and selected boards before synchronization and never treats an inaccessible private board as an empty board.
  5. Allow the first Trello synchronization to finish, then verify the expected resource population and member access policy.

3. Authorization and connection problems

Trello API key and token rejected
Confirm the trello api key and token is active, was entered without surrounding whitespace, and belongs to the intended Trello account and environment.
Missing permission or resource
Restore the exact read permission or provider-side resource access described in this guide. Seedling does not substitute a broader credential or silently treat a forbidden Trello population as empty.
Wrong account or scope
Disconnect before retrying with the intended Trello identity, account, and Seedling connection scope. Seedling does not infer account ownership from a display name or email address.

4. Missing or delayed data

  1. Confirm the board is visible to the token owner and included in the workspace or board allowlists.
  2. Check private-board membership, board closure, card archive, and workspace access changes.
  3. Allow per-key and per-token throttling retries to finish without broadening the token.
  4. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  5. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Create replacement trello api key and token for the same Trello account with the same or narrower released permissions.
  2. Replace the credential on the exact Seedling connection and repeat identity, scope, and capability verification.
  3. After Seedling confirms the replacement, revoke the old trello api key and token in Trello.