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

This node interacts with the Basecamp API to retrieve detailed information about a specific Message Type within a project. It is useful when you need to fetch metadata or configuration details of message categories (message types) defined in a Basecamp project, such as for reporting, automation, or integration purposes.

A practical example would be automating the retrieval of message type details to dynamically adjust workflows based on message categorization or to synchronize message type data with other systems.

Properties

Name	Meaning
Project ID	The numeric ID of the Basecamp project (bucket) where the message type resides. Used in the API endpoint path.
Category ID	The numeric ID of the message type (category) to retrieve. Used in the API endpoint path.
Return Full Response	Boolean option to return the entire HTTP response including status code and headers instead of just the response body.

Output

The node outputs JSON data representing the details of the requested message type. This typically includes all properties returned by the Basecamp API for that message type, such as its name, description, and any relevant metadata.

If the "Return Full Response" property is enabled, the output will include the full HTTP response object containing status code, headers, and body, allowing advanced users to handle response metadata.

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 access to the specified Basecamp account.
The node uses the Basecamp API base URL constructed from the authenticated account ID.
No additional external dependencies are required.

Troubleshooting

Invalid Project ID or Category ID: If the IDs provided do not exist or the user lacks permission, the API will return an error. Verify the IDs and ensure the credentials have appropriate access rights.
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 body may fail. Use this option only if you intend to process full HTTP responses.

Common error messages:

404 Not Found: The specified message type or project does not exist.
401 Unauthorized: Authentication failed; check credentials.
403 Forbidden: Insufficient permissions to access the resource.