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 subscribe to a specific resource identified by a bucket and recording within the Basecamp service. It is useful in scenarios where users want to receive updates or notifications related to particular projects or items they are interested in. For example, subscribing to a project bucket's recording enables the user to stay informed about changes or comments on that recording.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The numeric identifier of the bucket (project container) to which the subscription applies. |
| Recording Id | The numeric identifier of the specific recording (item or document) within the bucket to subscribe to. |
Output
The node outputs JSON data representing the result of the subscription action for the current user. This typically includes confirmation details such as subscription status or metadata about the subscribed item. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node uses the Basecamp API endpoint constructed dynamically based on the user's credentials.
- Proper configuration of the API authentication token and Basecamp account ID is necessary for successful requests.
Troubleshooting
Common issues:
- Invalid or missing Bucket Id or Recording Id will cause the subscription request to fail.
- Authentication errors if the API key or OAuth token is not configured correctly.
- Network or permission issues if the user does not have access rights to the specified bucket or recording.
Error messages:
- "Unauthorized" or "Authentication failed": Check API credentials and permissions.
- "Not Found" or "Resource does not exist": Verify that the Bucket Id and Recording Id are correct and accessible.
- "Bad Request": Ensure that all required parameters are provided and valid numbers.
Links and References
- Basecamp API Documentation
- n8n documentation on creating custom nodes