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 operation updates an existing Message Type within a specified project in Basecamp. A Message Type typically categorizes messages with a name and an emoji icon, helping organize communication threads or posts in the project management environment.

Common scenarios for this node include:

Renaming a message type to better reflect its purpose.
Changing the emoji icon associated with a message type to improve visual identification.
Adjusting message types as project needs evolve without creating new categories.

For example, you might update a "Bug Report" message type to "Issue Report" and change its icon from 🐞 to ⚠️ to better align with your team's terminology.

Properties

Name	Meaning
Project ID	The numeric ID of the project (bucket) where the message type exists. Used in API path.
Category ID	The numeric ID of the message type (category) to update. Used in API path.
Message Type Fields	Fields to update on the message type:
	- Name: New name for the message type.
	- Icon: Emoji icon representing the message type.
Return Full Response	Boolean flag indicating whether to return the full HTTP response (status, headers, body) or just the response body.

Output

The output JSON contains the updated message type data returned by the Basecamp API. This includes the updated fields such as the name and icon of the message type.

If "Return Full Response" is enabled, the output will include the entire HTTP response object, including status code, headers, and body.

No binary data output is involved in this operation.

Dependencies

Requires an authenticated connection to the Basecamp API using OAuth2 credentials.
The node uses the Basecamp API endpoint structured as https://3.basecampapi.com/{accountId}/buckets/{bucketId}/categories/{categoryId}.json for updating message types.
Proper permissions on the Basecamp account to modify message types are necessary.

Troubleshooting

Invalid Project or Category ID: If the provided IDs do not exist or the user lacks access, the API will return an error. Verify that the IDs are correct and accessible.
Authentication Errors: Ensure the OAuth2 credentials are valid and have not expired.
Missing Required Fields: Both Project ID and Category ID are required; missing these will cause the request to fail.
API Rate Limits: Frequent updates may hit rate limits imposed by Basecamp; handle errors accordingly.
Incorrect Field Values: Providing invalid emoji icons or empty names may result in validation errors from the API.