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 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 projects or recordings within Basecamp, such as automating reporting, monitoring subscription statuses, or integrating subscription details into other workflows.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | Numeric identifier of the bucket (project area) in Basecamp where the subscription exists. |
| Recording Id | Numeric identifier of the recording associated with the subscription to retrieve. |
Output
The node outputs JSON data representing the subscription details fetched from the Basecamp API. This typically includes all relevant fields describing the subscription's state, metadata, and any associated information returned by the API for the specified Bucket Id and Recording Id.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node uses the Basecamp API endpoint constructed dynamically using the authenticated user's Basecamp ID.
- Proper configuration of the API authentication credentials in n8n is necessary for successful requests.
Troubleshooting
Common issues:
- Invalid or missing Bucket Id or Recording Id will cause the API request to fail.
- Authentication errors if the API key or OAuth token is not configured correctly.
- Network connectivity problems can prevent reaching the Basecamp API.
Error messages:
- Unauthorized or 401 errors indicate invalid or expired credentials; re-authenticate or update credentials.
- 404 Not Found errors may mean the specified Bucket Id or Recording Id does not exist or is inaccessible.
- Rate limiting errors require waiting before retrying or adjusting API usage.