Actions80
- Todos Actions
- 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
Overview
This node watches for changes in a specific column within a card table (a structured collection of cards organized in columns and buckets). It is useful for scenarios where you want to trigger workflows based on updates or new entries in a particular column of a card table. For example, you might use it to monitor task status changes in a project management board or track new items added to a specific category.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The numeric identifier of the bucket containing the column to watch. This specifies which bucket's column changes will be monitored. |
| Column Id | The numeric identifier of the column to watch within the specified bucket. Changes in this column will trigger the node. |
Output
The node outputs JSON data representing the detected changes or current state of the watched column in the card table. The exact structure depends on the underlying API response but typically includes details about the cards in the column, their properties, and any updates that triggered the watch event.
If the node supports binary data output, it would represent attachments or files related to the cards, but this is not explicitly indicated in the provided code.
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 credentials within n8n.
- Depends on the external card table service's API to fetch and watch column data.
Troubleshooting
Common issues:
- Incorrect Bucket Id or Column Id values may result in no data being returned or errors.
- Authentication failures if the API key or token is missing or invalid.
- Network connectivity problems can prevent the node from reaching the external API.
Error messages:
- "Unauthorized" or "Authentication failed": Check that the API key credential is correctly configured.
- "Not Found" or similar: Verify that the Bucket Id and Column Id correspond to existing entities.
- Timeout or network errors: Ensure stable internet connection and that the API endpoint 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 using webhook/watch nodes for real-time triggers.