Trello

Trello is a lightweight project-management platform built around boards, lists, cards, checklists, and comments. In Agent Forge, the Trello block is focused on the parts of Trello that fit workflow automation best.

With Trello in Agent Forge, you can:

• inspect the current member and list accessible boards
• fetch boards, lists, cards, and checklists
• create and update cards and lists
• archive cards and lists
• create checklists, add check items, and update check item state
• fetch, edit, or delete comment actions
• search cards and boards
• trigger workflows from Trello webhook events such as createCard, updateCard, and commentCard

Usage Instructions

Use the Trello block when you want a workflow step or agent tool to call the Trello REST API with a connected Trello account.

Authentication

• Trello v1 in Agent Forge uses a public integration model: Forge owns the shared Trello API key and app secret, while each user connects their own Trello account.
• In the block, click Connect Trello or choose an existing Trello credential from the account selector.
• Forge opens Trello's token authorization flow, stores the returned user token as an encrypted credential, and uses the platform-owned TRELLO_API_KEY server-side.
• This integration still relies on Trello's API key + user token model under the hood because Trello Actions endpoints are not available to OAuth2/Forge apps.

Request Model

• Read operations use direct IDs such as boardId, cardId, listId, checklistId, checkItemId, and actionId.
• Write operations use the payload field.
• The payload field must be valid JSON and should contain Trello-compatible scalar fields such as name, idList, desc, closed, state, or value.
• Search uses query and optional modelTypes.

Good Fit

Use Trello when you want to:

• create cards from form submissions, tickets, or CRM events
• move or update cards as work changes state in other systems
• keep Trello checklists in sync with external approval or QA workflows
• react to Trello comments or card moves in downstream automations

Supported Operations

Boards and Member Context

• trello_get_current_member
• trello_list_boards
• trello_get_board
• trello_list_board_lists
• trello_list_board_cards

Cards

• trello_create_card
• trello_get_card
• trello_update_card
• trello_archive_card
• trello_add_card_comment

Lists

• trello_create_list
• trello_get_list
• trello_update_list
• trello_archive_list

Checklists

• trello_create_checklist
• trello_get_checklist
• trello_list_checklist_items
• trello_add_checkitem
• trello_update_checkitem

Actions

• trello_get_action
• trello_update_comment_action
• trello_delete_action

Search

• trello_search

Common Inputs

• credential: connected Trello account
• boardId: board identifier for board-scoped reads and optional search scoping
• cardId: card identifier for card, comment, checklist, and check item operations
• listId: list identifier for list operations
• checklistId: checklist identifier for checklist and check item reads
• checkItemId: check item identifier for check item updates
• actionId: action identifier for comment action reads and edits
• payload: JSON body for create and update actions

Example Payloads

Create a card

{
  "idList": "682b46list987",
  "name": "Follow up with design review",
  "desc": "Collect stakeholder feedback and final screenshots.",
  "pos": "top",
  "due": "2026-05-20T16:00:00.000Z"
}

Update a card

{
  "name": "Follow up with final design review",
  "idList": "682b46done123",
  "closed": false
}

Update a comment action

{
  "value": "Updated internal note after customer approval."
}

Trigger Support

Trello webhooks are available through the webhook trigger surface. Trello sends model-wide webhook events, so the recommended pattern is:

• subscribe to a board or card
• route Trello into a Forge webhook URL
• filter downstream on actionType

Supported Event Filters

The most automation-relevant Trello action types for v1 are:

• createCard
• updateCard
• commentCard

Setup Notes

• Trello validates the callback URL with an HTTP HEAD request before creating the webhook.
• Paste the generated Forge webhook URL into the Trello webhook callbackURL.
• Forge verifies the X-Trello-Webhook signature using the raw payload plus the exact callback URL and the platform-owned TRELLO_APP_SECRET.
• Trello webhook creation still happens on the Trello side for now; use a valid Trello credential for the board or model you want to watch.

Notes

• Category: tools
• Type: trello
• Required server config for public auth: TRELLO_API_KEY
• Required server config for webhook verification: TRELLO_APP_SECRET
• Trello Power-Ups, enterprise admin surfaces, and broad workspace admin APIs are intentionally out of scope for v1.
• Trello Actions resources used here are not available to Forge/OAuth2 apps, which is why Agent Forge uses Trello's token model behind the credential flow.