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 type of project management or organizational tool). It is designed to trigger workflows whenever there is an update or activity related to the specified column. This can be useful for automating notifications, syncing data, or triggering other processes based on changes in that column.
Practical examples include:
- Automatically sending alerts when tasks in a particular column are updated.
- Syncing column changes with external systems like CRMs or databases.
- Tracking progress by monitoring status columns in project boards.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The identifier of the bucket (or board) containing the card table. This specifies which board to watch. |
| Column Id | The 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 updated cards or items within that column, such as their IDs, content, and any metadata associated with the change.
If the node supports binary data output, it would relate to attachments or files linked to the cards, but this is not indicated in the provided code snippet.
Dependencies
- Requires an API key credential for authentication 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 API's webhook or polling capabilities to detect column changes.
Troubleshooting
Common issues:
- Incorrect Bucket Id or Column Id leading to no events being triggered.
- Authentication failures due to missing or invalid API credentials.
- Network connectivity problems preventing communication with the external API.
Error messages:
- "Unauthorized" or "Authentication failed": Check API credentials and permissions.
- "Resource not found": Verify that the Bucket Id and Column Id are correct and exist.
- "Timeout" or "Network error": Ensure stable internet connection and API availability.
Links and References
- Refer to the official documentation of the card table service for API details on buckets and columns.
- n8n documentation on creating and using webhook or polling nodes for watching resource changes.