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
The node interacts with the Basecamp API to retrieve details about a specific subscription. In particular, the "Get Subscription" operation under the "Subscriptions" resource fetches information about a subscription identified by a bucket ID and a recording ID. This is useful when you want to programmatically access subscription data related to specific buckets and recordings within Basecamp projects.
Practical examples include:
- Automating retrieval of subscription details for project management or reporting.
- Integrating subscription data into dashboards or other workflow automations.
- Triggering further actions based on subscription status or metadata.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | Numeric identifier of the bucket to which the subscription belongs. Required to specify the target subscription context. |
| Recording Id | Numeric identifier of the recording associated with the subscription. Required to identify the exact subscription record to retrieve. |
Output
The node outputs JSON data representing the subscription details fetched from the Basecamp API. The structure typically includes all relevant fields describing the subscription, such as its identifiers, status, timestamps, and any metadata provided by the API.
No binary data output is indicated in the source code.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node uses the Basecamp API base URL constructed dynamically using the authenticated user's Basecamp account ID.
- The node depends on the
@devlikeapro/n8n-openapi-nodepackage for building properties from the OpenAPI specification. - Proper configuration of the API credentials and permissions is necessary to access subscription data.
Troubleshooting
- Missing or invalid Bucket Id or Recording Id: Ensure both numeric IDs are provided and valid; otherwise, the API call will fail.
- Authentication errors: Verify that the API key or OAuth2 token is correctly configured and has sufficient permissions.
- Network or API errors: Check network connectivity and Basecamp API status if requests time out or return errors.
- Unexpected response structure: If the API changes, the node might not parse responses correctly; updating the node or API spec may be required.