Actions76
- Campfire Actions
- Card Table Actions
- Chatbot Actions
- Client Approval Actions
- Client Correspondence Actions
- Client Reply Actions
- Client Visibility Actions
- Comment Actions
- Document Actions
- Event Actions
- Forward Actions
- Inbox Actions
- Inbox Reply Actions
- Lineup Marker Actions
- Message Actions
- Message Board Actions
- Message Type Actions
- Person Actions
- Project Actions
- Question Actions
- Question Answer Actions
- Questionnaire Actions
- Recording Actions
Overview
This node interacts with the Basecamp API to retrieve a specific document from a given project (referred to as a "bucket" in the API). It is designed to fetch detailed information about a single document identified by its unique Document ID within a specified Project ID.
Common scenarios where this node is beneficial include:
- Automating workflows that require fetching document details for processing or reporting.
- Integrating Basecamp documents into other systems or dashboards.
- Triggering actions based on document content or metadata changes.
For example, you might use this node to automatically retrieve a project specification document when a new task is created, enabling further automation such as sending notifications or updating related records.
Properties
| Name | Meaning |
|---|---|
| Project ID | The ID of the project (bucket) containing the document. Used in the API endpoint path. |
| Document ID | The ID of the document to retrieve. Used in the API endpoint path. |
| Return Full Response | Whether to return the full HTTP response including status code and headers, or only the body. |
Output
The node outputs JSON data representing the requested document's details as returned by the Basecamp API. This typically includes metadata such as the document's title, content, creation date, author, and other relevant attributes.
If the "Return Full Response" property is enabled, the output will include the entire HTTP response object, which contains:
- Status code
- Headers
- Body (the document data)
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication.
- The node expects the user to provide valid Project ID and Document ID values.
- Proper API credentials must be configured in n8n to authenticate requests.
Troubleshooting
- Invalid Project ID or Document ID: If the IDs provided do not exist or are incorrect, the API will likely return a 404 Not Found error. Verify the IDs before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the OAuth2 credentials are correctly set up and authorized.
- API Rate Limits: Excessive requests may trigger rate limiting by Basecamp. Implement retry logic or reduce request frequency if needed.
- Return Full Response Misuse: Enabling "Return Full Response" changes the output structure. Downstream nodes expecting only the document body may fail. Use this option only when full HTTP response details are required.