Actions68
- Recordings Actions
- Card Tables Actions
- Forwards Actions
- Events Actions
- Projects Actions
- People Actions
- Chatbots Actions
- Webhooks Actions
- Attachments Actions
- Templates Actions
- Uploads Actions
- Documents Actions
- Lineup Markers Actions
- Subscriptions Actions
- Schedules Actions
- Schedule Entries Actions
Overview
This node watches for changes in a specific column within a card table (a Kanban-style board) in a project management or collaboration tool. It is useful for automating workflows that depend on updates to cards in a particular column, such as triggering notifications, updating other systems, or logging changes when cards move or are modified in that column.
For example, you could use this node to monitor the "In Progress" column of a task board and trigger an action whenever a new card enters that column, indicating work has started on a task.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The unique identifier of the bucket (board) containing the card table to watch. |
| Column Id | The unique identifier of the specific column within the bucket to monitor for changes. |
Output
The node outputs JSON data representing the event or change detected in the watched column. This typically includes details about the card(s) affected, such as their IDs, titles, status, and any relevant metadata reflecting the change.
If the node supports binary data output (not evident from the provided code), it would represent attachments or files related to the cards, but no such indication is present here.
Dependencies
- Requires an API key credential for authenticating with the external service hosting the card tables.
- Needs proper configuration of the API base URL and authentication headers.
- Depends on the external service's API supporting webhook or polling mechanisms to watch column changes.
Troubleshooting
Common Issues:
- Incorrect Bucket Id or Column Id leading to no events being captured.
- Authentication failures due to missing or invalid API credentials.
- Network connectivity issues preventing communication with the external API.
Error Messages:
- "Unauthorized" or "Authentication failed": Check that the API key or token is correctly configured and valid.
- "Resource not found": Verify that the Bucket Id and Column Id correspond to existing entities.
- Timeouts or connection errors: Ensure network access to the API endpoint is available.
Links and References
- Refer to the official API documentation of the card table service for details on bucket and column identifiers.
- Consult n8n documentation on setting up webhook or polling triggers for watching resource changes.