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 allows the current user to unsubscribe from a specific subscription in Basecamp by specifying the bucket and recording identifiers. It is useful when you want to programmatically stop receiving notifications or updates related to a particular item (recording) within a project bucket. For example, if a user no longer wants to follow changes on a certain document or discussion thread, this operation can be used to remove their subscription.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The numeric identifier of the project bucket that contains the subscription target. |
| Recording Id | The numeric identifier of the specific recording (e.g., message, document) to unsubscribe from. |
Output
The output JSON typically contains confirmation details about the unsubscription action. This may include status information or the updated subscription state for the current user. The exact structure depends on the Basecamp API response but generally confirms that the user is no longer subscribed to the specified recording.
No binary data output is expected from this operation.
Dependencies
- Requires an API authentication token configured in n8n to access the Basecamp API.
- The node uses the Basecamp API endpoint constructed with the user's Basecamp account ID.
- Proper permissions are needed to manage subscriptions for the current user.
Troubleshooting
- Invalid Bucket Id or Recording Id: If these IDs do not exist or the user does not have access, the API will return an error. Verify the IDs and user permissions.
- Authentication Errors: Ensure the API key or OAuth2 credentials are correctly set up and valid.
- Network Issues: Connectivity problems can cause request failures; check network settings.
- API Rate Limits: Excessive requests might be throttled by Basecamp; handle retries accordingly.
Links and References
- Basecamp API Documentation
- n8n Documentation on HTTP Request Nodes (for understanding API calls)