Actions119
- 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
- Schedule Actions
- Schedule Entry Actions
- Template Actions
- Todo Actions
- Todolist Actions
- Todolist Group Actions
- Todoset Actions
- Upload Actions
- Vault Actions
- Webhook Actions
Message Type → Destroy a Message Type
AI-generatedOverview
This node operation allows users to delete a specific message type within a project in Basecamp. It is useful for managing and cleaning up message types that are no longer needed in a project. For example, if a message type category is obsolete or created by mistake, this operation can remove it permanently.
Use Case Examples
- Deleting a message type category from a project to maintain organized communication channels.
- Removing an unused message type to prevent clutter in the project messaging system.
Properties
| Name | Meaning |
|---|---|
| Project ID | The ID of the project (bucket) where the message type exists. Used in the API endpoint path to specify the project. |
| categoryId | The ID of the message type (category) to be deleted. Used in the API endpoint path to specify which message type to destroy. |
| Return Full Response | Option to return the full HTTP response including status code, headers, and body instead of just the response body. |
| Request Options | Additional request settings such as batching, SSL certificate validation, proxy configuration, and timeout settings to customize the API request behavior. |
Output
JSON
statusCode- HTTP status code of the response indicating success or failure of the delete operation.headers- HTTP response headers returned by the API.body- The body of the response, typically containing confirmation or details of the deleted message type.
Dependencies
- Basecamp API with OAuth2 authentication
Troubleshooting
- Ensure the Project ID and categoryId are correct and correspond to existing resources; otherwise, the API will return an error indicating the resource was not found.
- If the user lacks sufficient permissions to delete the message type, the API will return an authorization error; verify the OAuth2 credentials have the necessary scopes.
- Network issues or incorrect proxy settings can cause request failures; check proxy configuration and network connectivity.
- If SSL certificate validation is disabled, be cautious of security risks; enable it unless necessary to bypass SSL issues.