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 interacts with the Basecamp API to retrieve information about a specific subscription. The "Get Subscription" operation fetches details of a subscription identified by a combination of a bucket ID and a recording ID. This is useful in scenarios where you need to programmatically access subscription data related to particular recordings within a project or workspace (bucket) in Basecamp.
Practical examples include:
- Automating retrieval of subscription details for reporting or auditing.
- Integrating subscription data into other workflows or systems.
- Monitoring subscription status or metadata changes for specific recordings.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | Numeric identifier of the bucket (project/workspace) that contains the subscription. |
| Recording Id | Numeric identifier of the recording associated with the subscription to be retrieved. |
Output
The node outputs JSON data representing the subscription details fetched from the Basecamp API. This typically includes all relevant fields describing the subscription, such as its status, associated recording info, timestamps, and any metadata provided by the API.
No binary data output is indicated by the source code.
Dependencies
- Requires an API authentication token configured via OAuth2 credentials for Basecamp.
- The node depends on the Basecamp API endpoint at
https://3.basecampapi.com/combined with the user's Basecamp account ID. - The bundled code uses an OpenAPI-based properties builder to define parameters and handle requests.
Troubleshooting
- Authentication errors: Ensure the OAuth2 credentials are correctly set up and authorized for the Basecamp account.
- Invalid IDs: Providing incorrect or non-existent bucket or recording IDs will result in API errors or empty responses.
- Network issues: Connectivity problems to the Basecamp API endpoint can cause request failures.
- Permission issues: The authenticated user must have sufficient permissions to access the specified bucket and recording.
Common error messages may include HTTP 401 Unauthorized, 404 Not Found (if IDs are invalid), or 403 Forbidden (insufficient permissions). Resolving these involves verifying credentials, input IDs, and user permissions.