Actions80
- Todos Actions
- 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
Overview
This node operation updates subscriptions for a specific recording within a bucket in the Basecamp service. It allows adding and removing people from the subscription list of a given recording. This is useful in scenarios where you want to manage who receives notifications or updates related to particular recordings, such as project meetings or audio logs.
Practical examples:
- Adding team members to receive updates on a new meeting recording.
- Removing users who no longer need to follow a specific recording's activity.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | Numeric identifier of the bucket containing the recording. |
| Recording Id | Numeric identifier of the recording whose subscriptions are being updated. |
| Subscriptions | JSON array of person IDs to subscribe (add) to the recording's notification list. |
| Unsubscriptions | JSON array of person IDs to unsubscribe (remove) from the recording's notification list. |
Output
The node outputs JSON data representing the result of the update subscription request. This typically includes confirmation of the updated subscription state or any relevant metadata returned by the Basecamp API. The output does not include binary data.
Dependencies
- Requires an API authentication token configured in n8n credentials to access the Basecamp API.
- The node uses the Basecamp API endpoint constructed with the user's Basecamp account ID.
- The request content type is JSON, and the node expects valid JSON arrays for subscriptions and unsubscriptions.
Troubleshooting
- Invalid Bucket Id or Recording Id: Ensure that the numeric IDs provided correspond to existing buckets and recordings in your Basecamp account.
- Malformed JSON in Subscriptions/Unsubscriptions: The properties expect valid JSON arrays. Invalid JSON will cause parsing errors.
- Authentication Errors: Verify that the API key or OAuth2 token is correctly set up and has sufficient permissions.
- Empty Subscription Arrays: Sending empty arrays may result in no changes; confirm intended behavior.
- API Rate Limits: Frequent updates might hit Basecamp API rate limits; handle retries accordingly.
Links and References
- Basecamp API Documentation
- n8n Documentation on HTTP Request Nodes (for understanding how JSON routing works)