Actions80
- Card Tables Actions
- Forwards Actions
- Events Actions
- Recordings 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
- Todo Sets Actions
- Todo Lists Actions
- Todos Actions
Overview
This node watches for changes in a specific column within a card table (a Kanban-style board). It is designed to trigger workflows when updates occur in the specified column, such as new cards being added, moved, or modified. This functionality is useful for automating processes that depend on real-time updates in project management or task tracking boards.
For example, you could use this node to:
- Automatically notify team members when a card moves into a "Ready for Review" column.
- Trigger follow-up tasks when a card is updated in a priority column.
- Sync changes from a card table column to another system or database.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The unique identifier of the bucket (board) containing the column to watch. |
| Column Id | The unique identifier of the column within the bucket to monitor for changes. |
Output
The node outputs JSON data representing the changes detected in the watched column. This typically includes details about the cards affected, such as their IDs, titles, statuses, and any other relevant metadata. The output allows subsequent nodes in the workflow to process these changes accordingly.
If the node supports binary data output (not indicated here), it would typically represent attachments or files related to the cards.
Dependencies
- Requires an API key credential for authenticating with the external service managing the card tables.
- Needs proper configuration of the API base URL and authentication tokens within n8n credentials.
- Depends on the external card table service's API to provide real-time or polling-based change detection.
Troubleshooting
Common Issues:
- Incorrect Bucket Id or Column Id values will result in no triggers firing because the node cannot find the specified column.
- Authentication failures due to invalid or expired API keys.
- Network connectivity issues preventing access to the external API.
Error Messages:
- "Unauthorized" — Check that the API key credential is correctly configured and has necessary permissions.
- "Resource not found" — Verify that the Bucket Id and Column Id are correct and exist in the external service.
- Timeout errors — Ensure stable network connection and that the external API is reachable.
Links and References
- Refer to the external card table service API documentation for details on bucket and column identifiers.
- n8n documentation on setting up API credentials and webhook/polling triggers.