> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/integrations/ticketing/trello.md).

# Trello

Connect Trello to Siit to escalate requests into Trello cards with one click. Trello is the right choice when ops, project, or marketing teams already manage their work on Trello boards.

### What you get

* **One-click escalation from any request.** Click **Escalate ticket** in the request side panel, pick a Trello board and list, and a linked card is created with the Siit context pre-filled.
* **Workflow-driven card creation.** Use **Create Trello card** as a workflow step, with approval gating where needed.
* **Audit trail.** Every Trello action triggered from Siit is recorded on the request timeline.

### How it works

1. From the request side panel, click **Escalate ticket** and pick **Trello**.
2. Choose the board, list, members, labels, and due date. Fill in the card name and description.
3. Submit. Siit creates the Trello card, links it back to the Siit request, and posts the link on both sides.

The same flow is available in workflows (as a **Create Trello card** action).

### What syncs from Trello

* **Cards created from Siit** — every escalated ticket is tracked with its Trello card ID and link.
* **Sync** is fully configurable and per-direction (`Settings → Workspace → Integration library → Trello → Settings`):
  * **Resolution** — resolve on one side, close on the other (with status mapping).
  * **Assignee** — reassignments mirror across.
  * **Notes** — internal notes sync.
  * **Messages** — new messages sync.
  * **Links** — bidirectional links stay visible on both sides.

### Custom field mapping

> **Coming soon.** Custom field mapping for Trello is on our roadmap. For now, you can set the standard card fields when escalating. To track which fields are exposed, reach out via the in-app chat.

### Connect Trello

1. In Siit, go to **Settings → Workspace → Integration library**, find **Trello** in the Ticketing section, and click **Connect**.
2. Sign in to Trello as an admin and approve the requested scopes.
3. Pick the workspace and board(s) available for escalation.
4. Test by escalating a sample request from Siit to Trello.

Need a more detailed walkthrough? Reach out to support via the in-app chat.

### Common workflows

**Marketing request handoff.** *Trigger: Service = "Marketing request". Actions: Create Trello card on the marketing board → Assign to the campaign lead → Notify requester.*

**Tag-based routing.** *Trigger: Tag "ops-task" added. Actions: Manager approval → Create Trello card on the ops board → Notify requester.*

### Troubleshooting

**"Authorization failed" on connect.** The admin signing in lacks workspace admin rights. Try with a Trello workspace admin.

**Board missing from the destination picker.** The Siit Trello user lacks access to that board. Update board membership in Trello and re-sync.

**"Card created" but no link in Siit.** The Trello card was created but the back-link save failed. Open the request timeline — the Trello card ID is logged. Manually re-link if needed.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.siit.io/integrations/ticketing/trello.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.