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 operation "Unwatch Column" for the "Card Tables" resource interacts with a project management or collaboration platform's API to stop watching (i.e., receiving notifications or updates) on a specific column within a card table. This is useful when users want to reduce notification noise or no longer need to track changes in that particular column.
Practical examples include:
- A team member who was previously monitoring progress on a task column but no longer needs updates.
- Automatically managing watch states based on workflow automation, such as unwatching columns after task completion.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The unique identifier of the bucket (or board) containing the card table. |
| Column Id | The unique identifier of the column within the specified bucket to unwatch. |
Output
The node outputs JSON data representing the result of the unwatch action. Typically, this would include confirmation of success or details about the updated watch state of the column. The exact structure depends on the API response but generally confirms that the column is no longer being watched.
No binary data output is involved.
Dependencies
- Requires an API key credential or OAuth2 token to authenticate requests to the external service hosting the card tables.
- The node relies on the Basecamp API (as indicated by the bundled source referencing Basecamp), so proper configuration of API credentials and base URL is necessary.
- Network access to the Basecamp API endpoint is required.
Troubleshooting
- Common issues:
- Invalid or missing Bucket Id or Column Id will cause the API call to fail.
- Authentication errors if the API key or OAuth token is invalid or expired.
- Network connectivity problems preventing access to the Basecamp API.
- Error messages:
- Unauthorized or 401 errors indicate authentication failure; verify credentials.
- 404 Not Found may mean the specified bucket or column does not exist.
- Rate limiting errors require waiting or adjusting request frequency.
Resolving these typically involves verifying input IDs, refreshing credentials, and ensuring network connectivity.
Links and References
- Basecamp API Documentation
- n8n documentation on creating custom nodes