Trello setup

Before connecting Trello

Use this page when the customer wants WebRiskOps to create or update Trello cards for remediation work. Trello is cloud-only, so setup should focus on the customer-owned workspace, board, list and card permissions instead of private-network or self-hosted URL checks. Start from `/settings` after Cloud and self-hosted integrations confirms Trello is a cloud target. Do not save a Trello token until the destination board, list, auth summary and revoke path are clear.

Connect a Trello board and list

Follow the path `Cloud and self-hosted integrations → Trello cloud target → Board and list mapping → Work management export → Revoke or fallback`.

1. Open /settings and review Integration status, then choose Trello setup. Result: provider_key is recorded as trello_cloud before board fields are requested.
2. Confirm Trello is a cloud-only target and leave base_url empty. Result: deployment_mode stays cloud and self-hosted network checks are not shown for Trello.
3. Choose the customer-owned Trello workspace and authorize with the supported auth_method. Result: WebRiskOps can list only the boards the customer allowed.
4. Select board_id and list_id for the card destination. Result: future work management exports know exactly where Trello cards should appear.
5. Confirm scopes for board, card, label and member lookup before saving. Result: WebRiskOps can map labels and checklist items without requesting unrelated Trello access.
6. Save only when the board, list and auth summary match the customer workflow. Result: Trello is available to work management export without exposing token values in documentation or support messages.
7. If PROVIDER_AUTH_REQUIRED appears, reconnect Trello before retrying. Result: the target stays blocked until valid cloud credentials exist.
8. If PROVIDER_SCOPE_UNAVAILABLE appears, adjust the Trello token or choose portable fallback. Result: cards are not created without the board and card permissions Trello requires.
9. Continue to Work management export after setup. Result: board_id, list_id, labels and checklist mapping use the same Trello provider record.

Configure Trello authorization

Trello setup should collect only the card destination and permissions the customer needs.

• `trello_cloud` is the only supported Trello provider key.
• `base_url` should stay empty because Trello does not have a self-hosted target.
• `auth_method` should identify the supported Trello token or OAuth-style flow before a credential is saved.
• `scopes` should allow board, card, label and member lookup for the selected workspace.
• `board_id` and `list_id` should be visible before Trello appears in work management export.
• Revoke access in Trello first, then disconnect the Trello target in WebRiskOps so historical cards keep references without keeping live credentials.

Ready Trello integration states

Continue only when the card destination is clear.

• Cloud target ready means `provider_key` is `trello_cloud` and `deployment_mode` is cloud.
• Board ready means `board_id` belongs to the customer-owned workspace.
• List ready means `list_id` points to the list where WebRiskOps should create or update cards.
• Scope ready means Trello can create cards and read labels or members needed for mapping.
• Revoke path ready means the customer knows how to revoke the Trello token before disconnecting WebRiskOps.

Blocked Trello setup states

Blocked Trello setup should explain exactly what to fix.

• `PROVIDER_AUTH_REQUIRED` means reconnect Trello before saving or retrying export.
• `PROVIDER_SCOPE_UNAVAILABLE` means the token cannot access the selected board, list, card fields or labels.
• A non-empty `base_url` means the customer is trying to use an unsupported self-hosted Trello target.
• Missing `board_id` or `list_id` means work management export cannot place the card.
• Required assignee, priority or component routing should use labels, checklist items or portable export notes when Trello does not expose matching fields.

Continue after Trello setup

Continue to Work management export when the Trello board and list are ready. Use Status sync and duplicate handling when a Trello card already exists, Portable export fallbacks when Trello permissions cannot be made safe, or Linear setup when the team uses Linear instead of Trello.