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
The node interacts with the Basecamp API to retrieve client approval data associated with a specific project. The "Get Client Approvals" operation fetches approvals related to a given project (referred to as a "bucket" in the API). This is useful for workflows that need to monitor or process client approvals within project management tasks, such as automating notifications when approvals are received or aggregating approval statuses for reporting.
Practical examples include:
- Automatically fetching all client approvals for a project to update a dashboard.
- Triggering follow-up actions when new approvals are detected.
- Integrating client approval data into other systems like CRMs or document management tools.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) for which client approvals are retrieved. Used in the API path. |
| Return All Results | Boolean option to either return all client approvals available or limit the results to a default maximum. |
| Return Full Response | Boolean option to return the entire HTTP response including status code and headers instead of just the body. |
Output
The node outputs JSON data representing the client approvals retrieved from the Basecamp API. The structure typically includes an array of approval objects with details such as approval status, approver information, timestamps, and related metadata.
If the "Return Full Response" property is enabled, the output will include the full HTTP response object containing:
- Status code
- Headers
- Body (the actual client approval 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 a valid project ID corresponding to a Basecamp bucket.
- Proper API credentials must be configured in n8n to authorize requests.
Troubleshooting
- Invalid Project ID: If the provided project ID does not exist or the user lacks access, the API may return a 404 or authorization error. Verify the project ID and permissions.
- Authentication Errors: Missing or expired OAuth tokens will cause authentication failures. Ensure credentials are correctly set up and refreshed.
- Pagination Issues: When "Return All Results" is enabled, pagination is handled automatically. However, if the API changes its pagination scheme, some results might be missed. Check API documentation for updates.
- Full Response Misuse: Enabling "Return Full Response" changes the output format. Downstream nodes expecting only the body may fail. Use this option only when full HTTP details are needed.
Links and References
- Basecamp API Documentation
- Basecamp Client Approvals Endpoint (for detailed schema and usage)