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 correspondence data associated with a specific project. The "Get Client Correspondences" operation fetches messages or communications related to a given project (referred to as a "bucket" in the API). This is useful for scenarios where users want to automate the retrieval of all client communications for project tracking, reporting, or integration with other systems.
Practical examples include:
- Automatically syncing client correspondence into a CRM or helpdesk system.
- Generating reports on client communication activity per project.
- Triggering workflows based on new client messages received in a project.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) from which to retrieve client correspondences. |
| Return All Results | Boolean flag indicating whether to return all available results or limit the output to a default count. |
| Return Full Response | Boolean flag indicating whether to return the full HTTP response (status code, headers, body) or just the body content. |
Output
The node outputs JSON data representing the client correspondences retrieved from the specified project. The structure typically includes an array of correspondence objects containing details such as message content, sender information, timestamps, and related metadata.
If the "Return Full Response" option is enabled, the output will include the entire HTTP response object, including status code and headers, allowing for more detailed handling or debugging.
The node does not output binary data.
Dependencies
- Requires an authenticated connection to the Basecamp API using OAuth2 credentials.
- The node expects the Basecamp account ID to be configured in the credentials to construct the API base URL.
- No additional external dependencies are required beyond the Basecamp API access.
Troubleshooting
Common Issues:
- Invalid or missing Project ID: Ensure the provided project ID exists and is accessible with the authenticated account.
- Authentication errors: Verify that the OAuth2 credentials are valid and have sufficient permissions.
- Pagination handling: When retrieving large datasets, ensure "Return All Results" is set appropriately to paginate through all pages.
Error Messages:
- Unauthorized or 401 errors indicate issues with authentication tokens; re-authenticate or refresh credentials.
- 404 errors may indicate the project ID does not exist or the user lacks access rights.
- Rate limiting errors from the API require implementing retry logic or waiting before subsequent requests.