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 operation "Unwatch Column" for the "Card Tables" resource interacts with a project management or collaboration platform's API to stop watching (i.e., unsubscribe from notifications or updates) 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 a particular column.
Practical examples include:
- A team member who was previously monitoring progress on a task column but no longer needs updates.
- Automating cleanup of watchers after a project phase ends.
- Managing notification preferences programmatically based on workflow conditions.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The unique identifier of the bucket (or board) that contains the card table. |
| Column Id | The unique identifier of the column within the card table that you want to unwatch. |
Output
The output JSON typically contains confirmation details about the unwatch action, such as success status or metadata about the updated watch state. It does not output binary data.
Example structure might include fields like:
{
"success": true,
"bucketId": 123,
"columnId": 456,
"message": "Column unwatched successfully"
}
Dependencies
- Requires an API key credential or OAuth2 token configured in n8n to authenticate requests against the external service managing card tables.
- The node depends on the Basecamp API or a similar project management API endpoint that supports watching/unwatching columns.
- Network access to the API endpoint is necessary.
Troubleshooting
- Invalid Bucket or Column Id: If the provided IDs do not exist or are incorrect, the API may return errors indicating resource not found. Verify IDs before running.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key or OAuth token is correctly set up.
- Permission Denied: The authenticated user must have permission to modify watch settings on the specified column.
- API Rate Limits: Excessive calls may trigger rate limiting; implement retries or backoff if needed.
Links and References
- Refer to the official API documentation of the project management tool for details on watching/unwatching columns.
- n8n documentation on setting up API credentials and using HTTP request nodes for custom integrations.