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 client correspondence within a project. It is useful when you need to fetch detailed information about a particular piece of communication or document exchanged with a client, identified by its unique correspondence ID and associated project ID.
Typical use cases include:
- Automating retrieval of client messages or documents for processing or archival.
- Integrating client correspondence data into other systems such as CRMs or reporting tools.
- Triggering workflows based on specific client communications.
For example, you might use this node to get the details of a client email or message stored in Basecamp related to a certain project, then analyze or forward that information automatically.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) where the client correspondence resides. |
| Correspondence ID | The numeric ID of the specific client correspondence to retrieve. |
| Return Full Response | Boolean flag indicating whether to return the entire HTTP response (status code, headers, body) or just the response body. |
Output
The node outputs JSON data representing the client correspondence retrieved from Basecamp. This typically includes all details about the correspondence such as content, timestamps, sender/recipient info, and metadata.
If the "Return Full Response" property is enabled, the output will include the full HTTP response object containing status code, headers, and body instead of only the correspondence data.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication.
- The node expects the user to provide valid project and correspondence IDs.
- Proper API credentials must be configured in n8n to authorize requests.
Troubleshooting
- Invalid IDs: If the project ID or correspondence ID does not exist or is 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 the requested resources.
- Network issues: Connectivity problems can cause request failures; check network settings and Basecamp service status.
- Full response confusion: When enabling "Return Full Response," users may see unexpected data structures. Disable this option if only the correspondence content is needed.