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 node interacts with the Basecamp API to retrieve detailed information about a specific message within a project (referred to as a "bucket" in Basecamp terminology). This operation is useful when you want to fetch the content and metadata of a particular message posted in a Basecamp project.

Common scenarios include:

Automating workflows that require fetching message details for processing or archiving.
Integrating Basecamp messages into other systems like CRMs, help desks, or reporting tools.
Triggering actions based on message content or status updates.

For example, you might use this node to get the full details of a message by its ID within a given project to display it in a custom dashboard or to analyze communication patterns.

Properties

Name	Meaning
Project ID	The numeric ID of the Basecamp project (bucket) where the message resides.
Message ID	The numeric ID of the specific message to retrieve.
Return Full Response	Boolean option to return the entire HTTP response including status code and headers, or just the message body.

Output

The node outputs JSON data representing the retrieved message's details from Basecamp. This typically includes fields such as the message content, author, timestamps, attachments, and other metadata provided by the Basecamp API.

If the "Return Full Response" property is enabled, the output will include the full HTTP response object containing status code, headers, and body, allowing more advanced handling of the API response.

The node does not output binary data.

Dependencies

Requires an active connection to the Basecamp API using OAuth2 authentication.
The user must provide valid credentials with appropriate permissions to access the specified project and message.
The node uses the Basecamp API base URL constructed dynamically from the user's account ID.

Troubleshooting

Invalid Project or Message ID: If the IDs provided do not exist or the authenticated user lacks access, the API will return an error. Verify the IDs and permissions.
Authentication Errors: Ensure the OAuth2 credentials are correctly configured and have not expired.
API Rate Limits: Excessive requests may lead to rate limiting; handle retries or backoff accordingly.
Return Full Response Misuse: Enabling "Return Full Response" changes the output format; downstream nodes expecting only the message body may fail if not adjusted.