AsyncAPI channel · trello · Trello Webhooks Events

/webhook

Callback endpoint that receives webhook events from Trello via HTTP POST when any action occurs on the watched model. The callback URL must return a 200 status code on HEAD requests for webhook creation and on POST requests to acknowledge delivery.

Provider: trello AsyncAPI: v2.6.0 Spec: Trello Webhooks Events Operations: 1 Messages: 10

Channel address

/webhook

Operations

publish
receiveWebhookEvent
Receive a Trello webhook event

Messages

BoardEvent
An action that occurred on a board, such as creating, updating, closing, or deleting a board.
Content-Type: application/json
CardEvent
An action that occurred on a card, such as creating, updating, moving, archiving, or deleting a card.
Content-Type: application/json
ListEvent
An action that occurred on a list, such as creating, renaming, archiving, or moving a list.
Content-Type: application/json
MemberEvent
An action involving a member, such as adding or removing a member from a board or card.
Content-Type: application/json
ChecklistEvent
An action involving a checklist or check item, such as creating a checklist, adding a check item, or completing a check item.
Content-Type: application/json
OrganizationEvent
An action that occurred on an organization (workspace), such as updating settings or managing members.
Content-Type: application/json
LabelEvent
An action involving a label, such as creating, updating, or deleting a label, or adding or removing a label from a card.
Content-Type: application/json
CommentEvent
An action involving a comment on a card, such as adding, updating, or deleting a comment.
Content-Type: application/json
AttachmentEvent
An action involving an attachment, such as adding or removing an attachment from a card.
Content-Type: application/json
CustomFieldEvent
An action involving custom fields, such as creating a custom field definition or setting a custom field value on a card.
Content-Type: application/json

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.