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 detailed information about a specific client approval within a project. It is useful when you need to programmatically access the status, details, or metadata of a client approval item in Basecamp projects. For example, it can be used in workflows that automate project management tasks, such as notifying team members when a client approval is retrieved or integrating approval data into reporting dashboards.
Properties
Name | Meaning |
---|---|
Project ID | The ID of the project (bucket) where the client approval resides. Used in the API path. |
Approval ID | The unique ID of the client approval to retrieve. Used in the API path. |
Return Full Response | Boolean flag indicating whether to return the full HTTP response (status code, headers, body) or just the response body. |
Output
The node outputs JSON data representing the client approval details fetched from the Basecamp API. If "Return Full Response" is set to true, the output includes the entire HTTP response object containing status code, headers, and body; otherwise, only the body (the client approval data) is returned.
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 and approval IDs.
- The Basecamp account ID must be configured in the credentials to construct the API base URL.
Troubleshooting
- Invalid Project or Approval ID: If the provided IDs do not exist or are incorrect, the API will likely return a 404 error. Verify the IDs before running the node.
- Authentication Errors: Ensure the OAuth2 credentials are correctly set up and have sufficient permissions to access client approvals.
- API Rate Limits: Frequent requests may hit Basecamp API rate limits, causing errors. Implement retry logic or reduce request frequency.
- Return Full Response Misuse: Setting "Return Full Response" to true changes the output format. Downstream nodes expecting only the body might fail if this is enabled unintentionally.