Files
wehub-resource-sync 4b6817381b
CI (OpenClaw E2E) / openclaw test (push) Has been cancelled
CI / coverage-report (push) Has been cancelled
CI / test-kubernetes (push) Has been cancelled
CI / should-run-thorough (push) Has been cancelled
CI / test-thorough (cloudwatch-demo) (push) Has been cancelled
CI / test-thorough (flink-ecs) (push) Has been cancelled
CI / test-thorough (upstream-lambda) (push) Has been cancelled
CI / test-thorough (prefect-ecs-fargate) (push) Has been cancelled
Release / build-binaries (zip, opensre.exe, onefile, windows-latest, windows-x64) (push) Has been cancelled
Benchmark image — build + push to ECR (any adapter) / build + push (push) Has been cancelled
CI / quality (ubuntu-latest) (push) Has been cancelled
CI / test (tools-runtime) (push) Has been cancelled
CI / test (e2e-general) (push) Has been cancelled
CI / test (cli-runtime) (push) Has been cancelled
CI / test (e2e-provider-and-openclaw) (push) Has been cancelled
CI / test (integrations-and-misc) (push) Has been cancelled
Release / verify (push) Has been cancelled
Release / build-python-dist (push) Has been cancelled
Release / build-binaries (tar.gz, opensre, onedir, macos-15-intel, darwin-x64) (push) Has been cancelled
Release / build-binaries (tar.gz, opensre, onedir, macos-latest, darwin-arm64) (push) Has been cancelled
Release / build-binaries (tar.gz, opensre, onedir, ubuntu-22.04, linux-x64) (push) Has been cancelled
Release / publish-release (push) Has been cancelled
Release / publish-main-release (push) Has been cancelled
Interactive Shell Live (PR + post-merge) / turn-checks (no-LLM) (push) Has been cancelled
CodeQL / Analyze (python) (push) Has been cancelled
Interactive Shell Live (PR + post-merge) / turn-live shard ${{ matrix.shard_index }} (push) Has been cancelled
Release / prepare (push) Has been cancelled
Release / build-binaries (tar.gz, opensre, onedir, ubuntu-22.04-arm, linux-arm64) (push) Has been cancelled
Synthetic Deterministic Tests / Synthetic offline (deterministic) (push) Has been cancelled
chore: import upstream snapshot with attribution
2026-07-13 13:10:45 +08:00

118 lines
3.4 KiB
Plaintext

---
title: "Trello"
description: "Connect Trello so OpenSRE can view cards and boards during investigations and incident management"
---
When incidents happen, keeping everyone organized matters. OpenSRE connects to Trello so you can create incident cards, track investigation progress, and manage follow-up tasks — all without leaving your incident response workflow.
## What you need
- A Trello account with access to the boards you want OpenSRE to use
- A Trello API key and token
- Optional board and list IDs for automatic card creation
## Setting up Trello
### Quick setup
```bash
opensre integrations setup
```
Choose **Trello** and enter your API key and token when prompted.
### Manual config: Environment variables
Or add these to your `.env`:
```bash
TRELLO_API_KEY=your_api_key
TRELLO_TOKEN=your_token
TRELLO_BOARD_ID=board_id_optional
TRELLO_LIST_ID=list_id_optional
TRELLO_BASE_URL=https://api.trello.com/1
```
| Variable | Default | Description |
| --- | --- | --- |
| `TRELLO_API_KEY` | — | **Required.** Trello API key |
| `TRELLO_TOKEN` | — | **Required.** Trello API token |
| `TRELLO_BOARD_ID` | *(empty)* | Optional default board ID for card creation |
| `TRELLO_LIST_ID` | *(empty)* | Optional default list ID for card creation |
| `TRELLO_BASE_URL` | `https://api.trello.com/1` | Trello API base URL |
### Persistent store
You can also save your Trello configuration to `~/.opensre/integrations.json`:
```json
{
"version": 1,
"integrations": [
{
"id": "trello-prod",
"service": "trello",
"status": "active",
"credentials": {
"api_key": "your_api_key",
"token": "your_token",
"board_id": "board_id_optional",
"list_id": "list_id_optional"
}
}
]
}
```
## Getting your API key and token
1. Visit https://trello.com/app-key
2. Copy your Trello API key
3. Generate a token from the same page
4. Authorize access when prompted
5. Store both values securely
## Optional: Finding board and list IDs
If you'd like OpenSRE to create cards in a specific location, you'll need the board and list IDs.
### Using the API
```bash
curl "https://api.trello.com/1/members/me/boards?key=${TRELLO_API_KEY}&token=${TRELLO_TOKEN}"
```
### Manual method
1. Open the board in Trello
2. Append `.json` to the board URL
3. Search the response for the board ID
4. Locate the desired list and copy its ID
## Token longevity
Trello tokens can be created with different expiration periods. When generating a token, choose an expiration period that aligns with your organization's security requirements.
For long-lived OpenSRE integrations, consider using an appropriately scoped token and rotating it regularly according to your security policies.
## Required permissions
Your Trello token should have:
- **read** — Allows OpenSRE to view boards, lists, and cards
- **write** — Allows OpenSRE to create or update cards during investigations
## Usage
Once configured, OpenSRE can:
- Create Trello cards from investigation findings
- Send incident titles and descriptions to a target list
- Track follow-up tasks on your incident board
Set `TRELLO_LIST_ID` to the list where new cards should appear. If omitted, card creation requires the list ID at investigation time.
<Info>
Trello does not currently support `opensre integrations verify trello`. Confirm your credentials during interactive setup or by creating a test card from an investigation.
</Info>