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 replies associated with a specific project and recording. It is designed to fetch all or a limited number of client replies (correspondences or approvals) linked to a given recording within a project.
This node is beneficial in scenarios where users need to automate the retrieval of client feedback, comments, or approvals from Basecamp projects for further processing, reporting, or integration with other systems.
Practical examples:
- Automatically fetching all client replies related to a particular project milestone to generate status reports.
- Integrating client feedback into a CRM or support system by retrieving replies from Basecamp recordings.
- Monitoring client approvals or correspondences programmatically to trigger subsequent workflow steps.
Properties
| Name | Meaning |
|---|---|
| Project ID | The ID of the project (bucket). Used in the API endpoint path to specify which project to query. |
| Recording ID | The ID of the recording (client correspondence or client approval). Used in the API endpoint path. |
| Return All Results | Whether to return all client replies or only up to a given limit. Boolean option: true or false. |
| Return Full Response | Whether to return the full HTTP response including status code, headers, and body, instead of only body. |
Output
The node outputs JSON data representing the client replies retrieved from the Basecamp API. The structure typically includes an array of client reply objects containing details such as message content, author information, timestamps, and any metadata provided by the API.
If the "Return Full Response" property is enabled, the output will include the entire HTTP response object, encompassing status code, headers, and body, allowing advanced handling of response metadata.
The node does not output binary data.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication.
- Needs configuration of an API authentication token credential within n8n to authorize requests.
- The base URL for API requests is constructed dynamically using the account ID from credentials.
Troubleshooting
Common issues:
- Invalid or missing Project ID or Recording ID will result in API errors or empty responses.
- Insufficient permissions or expired API tokens may cause authorization failures.
- Network connectivity problems can prevent successful API calls.
Error messages and resolutions:
- 401 Unauthorized: Check that the API authentication token is valid and has not expired.
- 404 Not Found: Verify that the specified Project ID and Recording ID exist and are accessible.
- 429 Too Many Requests: The API rate limit has been exceeded; implement retry logic or reduce request frequency.
- 500 Internal Server Error: Temporary server issue; retry after some time or contact Basecamp support if persistent.
Links and References
- Basecamp API Documentation
- Basecamp Client Replies Endpoint (for detailed API schema and usage)