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 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 now wants to stop receiving updates.
- Automating cleanup of watchers on columns after a project phase ends.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The unique identifier of the bucket (a container or grouping of cards) containing the column to unwatch. |
| Column Id | The unique identifier of the column within the specified bucket that should be unwatched. |
Output
The node outputs JSON data representing the result of the "unwatch column" action. Typically, this would confirm success or provide details about the updated watch status of the column. The exact structure depends on the API response but generally includes confirmation fields or metadata about the unwatch operation.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the external service managing card tables.
- The node uses a base URL constructed dynamically from credentials (e.g., a Basecamp ID).
- The underlying API expects JSON requests and responses.
- Proper configuration of authentication credentials in n8n is necessary.
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 not set up correctly.
- Network connectivity problems can prevent reaching the API endpoint.
Error messages:
- Unauthorized or 401 errors indicate invalid or expired credentials; re-authenticate or update credentials.
- 404 Not Found may mean the specified bucket or column does not exist; verify IDs.
- 400 Bad Request could indicate malformed input parameters; ensure Bucket Id and Column Id are numbers and valid.
Resolving these typically involves verifying input parameters, checking credential validity, and ensuring network access.
Links and References
- Refer to the official API documentation of the card table service for details on the "unwatch column" endpoint.
- n8n documentation on setting up API credentials and using HTTP request nodes for custom API calls.