Basecamp

Interact with Basecamp API

Actions76

Campfire Actions
- Create a Campfire Line
- Delete a Campfire Line
- Get a Campfire
- Get a Campfire Line
- Get Campfire Lines
- Get Campfires
Card Table Actions
- Create a Card
- Create a Column
- Get a Card
- Get a Card Table
- Get a Column
- Get Cards in a Column
- Move a Card
- Move a Column
- Update a Card
- Update a Column
Chatbot Actions
- Create a Chatbot
- Create a Chatbot Line
- Delete a Chatbot
- Get a Chatbot
- Get All Chatbots
- Update a Chatbot
Client Approval Actions
- Get a Client Approval
- Get Client Approvals
Client Correspondence Actions
- Get a Client Correspondence
- Get Client Correspondences
Client Reply Actions
- Get Client Replies
- Get a Client Reply
Client Visibility Actions
- Toggle Client Visibility
Comment Actions
- Get Comments
- Create a Comment
- Get a Comment
- Update a Comment
Document Actions
- Get Documents
- Create a Document
- Get a Document
- Update a Document
Event Actions
- Get Events
Forward Actions
- Get Forwards
- Get a Forward
Inbox Actions
- Get Inbox
Inbox Reply Actions
- Get Inbox Replies
- Get an Inbox Reply
Lineup Marker Actions
- Create a Marker
- Update a Marker
- Delete a Marker
Message Actions
- Get Messages
- Create a Message
- Get a Message
- Update a Message
Message Board Actions
- Get Message Board
Message Type Actions
- Create a Message Type
- Destroy a Message Type
- Get a Message Type
- Get Message Types
- Update a Message Type
Person Actions
- Get a Person
- Get My Profile
- Get People
- Get People on a Project
- Manage People on a Project
Project Actions
- Create a Project
- Get a Project
- Get Projects
- Trash a Project
- Update a Project
Question Actions
- Get Questions
- Create a Question
- Get a Question
- Update a Question
Question Answer Actions
- Get Question Answers
- Get a Question Answer
Questionnaire Actions
- Get Questionnaire
Recording Actions
- Get Recordings
- Trash a Recording
- Archive a Recording

Overview

The "Get an Inbox Reply" operation in the Basecamp node retrieves a specific reply from an inbox forward within a project. This is useful when you want to access detailed information about a particular reply message that was sent or received in the context of a project’s inbox communication.

Common scenarios include:

Fetching the content and metadata of a reply to display or process it further.
Integrating with other systems to track communication threads.
Automating workflows based on replies received in project inboxes.

For example, you might use this node to get the details of a customer support reply stored in a Basecamp project inbox to trigger follow-up actions or logging.

Properties

Name	Meaning
Project ID	The ID of the project (bucket) where the inbox forward exists; used in the API endpoint path.
Forward ID	The ID of the forward message within the inbox; used in the API endpoint path.
Reply ID	The ID of the specific reply to retrieve; used in the API endpoint path.
Return Full Response	Boolean flag indicating whether to return the full HTTP response (status code, headers, body) or just the body content.

Output

The output JSON contains the data of the requested inbox reply. This typically includes all details returned by the Basecamp API for that reply, such as the reply content, author information, timestamps, and any associated metadata.

If the "Return Full Response" property is set to true, the output will include the entire HTTP response object, which contains:

Status code of the request
Response headers
Body with the reply data

Otherwise, only the reply data (body) is returned.

The node does not output binary data.

Dependencies

Requires an active connection to the Basecamp API using OAuth2 authentication.
The node expects the user to provide valid project, forward, and reply IDs.
Proper API credentials must be configured in n8n to authenticate requests.

Troubleshooting

Invalid IDs: If the provided Project ID, Forward ID, or Reply ID do not exist or are incorrect, the API will likely return a 404 error. Verify these IDs carefully.
Authentication errors: Missing or invalid API credentials will cause authentication failures. Ensure the OAuth2 credentials are correctly set up.
Permission issues: The authenticated user must have access rights to the specified project and its inbox messages.
Return Full Response confusion: If enabled, the output structure changes to include status and headers, which may require adjusting downstream nodes to handle this format.