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
The "Unwatch Column" operation in the "Card Tables" resource allows users to stop watching a specific column within a card table. Watching a column typically means receiving notifications or updates about changes in that column. This operation is useful when a user no longer wants to be notified about updates or activities related to a particular column, helping reduce notification noise and focus on relevant information.
Practical examples:
- A project manager stops watching a column representing completed tasks after the project phase ends.
- A team member unsubscribes from updates on a backlog column once their work on those items is done.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The unique identifier of the bucket (card table) containing the column to unwatch. |
| Column Id | The unique identifier of the column to stop watching. |
Output
The node outputs JSON data representing the result of the unwatch action. Typically, this would include confirmation that the column is no longer being watched or details about the updated watch status. The exact structure depends on the API response but generally confirms success or failure of the operation.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node uses the Basecamp API endpoint corresponding to card tables and columns.
- Proper configuration of the Basecamp API credentials and base URL is necessary.
Troubleshooting
- Invalid Bucket Id or Column Id: If the provided IDs do not exist or are incorrect, the API will likely return an error indicating the resource was not found. Verify the IDs before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key or OAuth token is correctly configured.
- Permission Issues: The authenticated user must have permission to modify watch settings on the specified column. Lack of permissions will result in authorization errors.
- Network or API Downtime: Connectivity issues or Basecamp API downtime can cause request failures. Retry later or check network connectivity.