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 updates subscriptions for a specific recording within a bucket in the Basecamp system. It allows you to add or remove people from the subscription list of a given recording, effectively managing who receives updates or notifications related to that recording.
Common scenarios include:
- Managing notification recipients for project recordings.
- Dynamically adjusting subscription lists based on user actions or external triggers.
- Automating subscription updates when team members join or leave projects.
For example, you might use this node to subscribe new team members to a meeting recording so they receive updates, or unsubscribe former members who no longer need access.
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 add as subscribers to the recording. |
| Unsubscriptions | A JSON array of person IDs to remove from the recording's subscriber 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 credential configured in n8n to authenticate requests to 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 subscription changes.
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: Ensure that the JSON arrays for subscriptions and unsubscriptions are correctly formatted. Invalid JSON will cause parsing errors.
- Authentication Errors: Missing or invalid API credentials will prevent the node from successfully updating subscriptions. Confirm that the API key/token is correctly set up.
- Empty Subscription Arrays: Passing empty arrays may result in no changes; ensure that the arrays contain valid person IDs if updates are intended.
Links and References
- Basecamp API Documentation - Official API docs for managing subscriptions and other resources.
- n8n Documentation - General guidance on using credentials and JSON input properties in n8n nodes.