Reference · Tools

Trello Trigger

Starts workflow when Trello events occur on a watched board, list, or card

Webhook trigger Productivity v1

The Trello Trigger watches a Trello model — a board, list or card — and starts a workflow on any action against it. Because every action type fires, filtering to the ones you care about happens downstream. A typical build is reacting when cards move into a particular list.

Node type
Webhook trigger
Parameters
1
Outputs
Output
Credentials
Trello API

Trello Trigger

Trigger workflows from Trello board, list, and card events

Overview

The Trello Trigger node listens for webhook events from Trello. It watches a specific model (board, list, or card) identified by its ID and fires whenever actions occur on that model. Trello delivers action payloads containing the action type (e.g., createCard, updateCard, moveListFromBoard), the member who performed it, and the affected model data. The trigger handles Trello’s HEAD verification request automatically. Use this to start workflows based on any Trello activity such as card creation, movement, comments, member changes, label updates, checklist modifications, and more.

Category: Productivity
Tool Name: trello_trigger
Version: 1

Appearance: Icon: si-trello | Color: #0079bf

Node Type

Trigger — webhook (receives incoming HTTP callbacks)

Input / Output

DirectionPort(s)
InputNone (trigger node)
OutputOutput

Credentials

This tool requires Trello API credentials. See the Credentials Guide for setup instructions.

Parameters

ParameterTypeRequiredDefaultDescription
Model IDstringYesID of the Trello board, list, or card to watch for events. You can find this in the URL when viewing the item on Trello.

Output Data

Each Trello action on the watched model produces one output item:

  • action — the full Trello action object
  • model — the full Trello model (board, list, or card) the action applied to
  • actionType — the action type, e.g. createCard, updateCard, commentCard
  • actionId — the ID of the action
  • actionDate — the timestamp Trello recorded for the action
  • memberCreator — the Trello member who performed the action
  • actionData — the action’s data payload (the changed fields, card, list and board references)
  • modelId — the ID of the watched model
  • modelName — the name of the watched model
  • _trigger — always trello_webhook
  • _timestamp — ISO 8601 timestamp of when the action was received
  • _webhookEvent — the same value as actionType

Every action type on the model is delivered, so filter downstream on actionType when you only care about some of them.

Reference the payload downstream by expression, e.g. {{ $json.actionData.card.name }}.

Usage Examples

  • Start a workflow when a new card is created on a Trello board
  • Trigger automation when a Trello card is moved to a different list
  • React to comments added on Trello cards
  • Monitor member additions or removals on a Trello board
  • Automate actions when checklists or labels are updated in Trello

Example Configuration

Watch a board for all activity:

{
  "type": "trello_trigger",
  "parameters": {
    "modelId": "4d5ea62fd76aa1136000000c"
  }
}

Watch a single card:

{
  "type": "trello_trigger",
  "parameters": {
    "modelId": "5f8a1b2c3d4e5f6a7b8c9d0e"
  }
}

Trigger Behavior

  • Activation: When the workflow is activated, a webhook endpoint is registered with the service.
  • Deactivation: The webhook is automatically unregistered when the workflow is deactivated.
  • Payload: The incoming webhook payload is parsed and output as workflow items.
  • Verification: Supports signature verification where applicable.

Tips

Watches a Trello model (board, list, or card) for any actions. Provide the model ID to monitor. All Trello action types on that model will trigger this node. Use downstream filtering to act on specific action types.

Frequently asked questions

Can I subscribe to only certain action types?

Not on the trigger itself — all Trello action types on the watched model fire it. Use an If or Switch node immediately after to act on the specific types you handle.

What do I configure?

The model ID to monitor, which can be a board, a list or a card depending on how narrowly you want to watch.

Will it be noisy?

On an active board, yes — which is why downstream filtering matters. Watching a specific list or card is quieter than watching a whole board.

Which credential does it need?

A Trello API credential, the same one the action node uses.

Build with the Trello Trigger node

Drop it into a workflow, wire it to an agent, or call it on a schedule. You'll need Trello API credentials first.

Open BusyBot

Last updated . Spotted something wrong? Tell us.