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 updates subscriptions for a specific recording within a bucket in the Basecamp service. It allows adding and removing people from subscription lists associated with a particular recording. This is useful in scenarios where you want to manage who receives notifications or updates related to certain recordings, such as project meetings, audio logs, or other recorded content.
Practical examples include:
- Adding team members to receive updates about a new meeting recording.
- Removing users who no longer need to be notified about changes to a recording.
- Managing subscription lists dynamically based on project roles or changes in team composition.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The numeric identifier of the bucket containing the recording to update subscriptions for. |
| Recording Id | The numeric identifier of the recording whose subscriptions are being updated. |
| Subscriptions | A JSON array of person IDs to subscribe (add) to the recording's subscription list. |
| Unsubscriptions | A JSON array of person IDs to unsubscribe (remove) from the recording's subscription list. |
Output
The node outputs JSON data representing the result of the subscription update operation. This typically includes confirmation of the updated subscription state or any relevant metadata returned by the Basecamp API. There is no indication that binary data is output by this node.
Dependencies
- Requires an API authentication token configured via OAuth2 credentials to access the Basecamp API.
- The node uses the Basecamp API endpoint constructed with the user's Basecamp account ID.
- The request headers specify JSON content type and accept JSON responses.
Troubleshooting
- Invalid Bucket or Recording Id: If the provided bucket or recording IDs do not exist or are incorrect, the API will likely return an error. Verify these IDs before running the node.
- Malformed JSON in Subscriptions/Unsubscriptions: Since these fields expect JSON arrays, ensure the input is valid JSON. Parsing errors will cause the node to fail.
- Authentication Errors: Ensure the OAuth2 credentials are correctly set up and have sufficient permissions to modify subscriptions.
- Empty Subscription Arrays: Passing empty arrays may result in no changes; confirm intended behavior when no subscriptions or unsubscriptions are specified.