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 allows the current user to unsubscribe from a specific subscription within Basecamp. It targets a particular recording inside a bucket, effectively removing the user's subscription to updates or notifications related to that recording. This is useful in scenarios where users want to stop receiving alerts or updates about certain project elements they no longer wish to follow.
Practical examples include:
- A team member unsubscribing from notifications on a completed task or discussion thread.
- Automatically managing subscriptions based on workflow conditions, such as unsubscribing users from recordings after a milestone is reached.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The unique identifier of the bucket containing the recording to unsubscribe from. |
| Recording Id | The unique identifier of the recording (e.g., message, document) from which to unsubscribe. |
Output
The node outputs JSON data representing the result of the unsubscribe action. Typically, this will confirm whether the unsubscription was successful or provide details about the updated subscription status. There is no indication that binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node depends on the Basecamp API endpoint for managing subscriptions.
- Proper configuration of the Basecamp account ID and OAuth2 credentials within n8n is necessary for successful API calls.
Troubleshooting
Common issues:
- Invalid or missing Bucket Id or Recording Id can cause the API call to fail.
- Authentication errors if the API key or OAuth token is not correctly configured.
- Permission errors if the authenticated user does not have access to the specified bucket or recording.
Error messages and resolutions:
- "Unauthorized" or "Authentication failed": Verify that the API credentials are valid and properly set up.
- "Not Found" or "Resource does not exist": Check that the Bucket Id and Recording Id are correct and correspond to existing resources.
- "Forbidden": Ensure the user has sufficient permissions to unsubscribe from the given recording.