Actions76
- 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
Overview
This node interacts with the Basecamp API to manage "Message Types" within a project. Specifically, the "Destroy a Message Type" operation deletes a message type (category) from a specified project (bucket). This is useful for cleaning up or reorganizing message categories that are no longer needed in a Basecamp project.
Practical examples include:
- Removing obsolete or redundant message types from a project to maintain clarity.
- Automating cleanup of message categories as part of project lifecycle management.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) where the message type exists. Used in the API path. |
| categoryId | The numeric ID of the message type (category) to be deleted. Used in the API path. |
| Return Full Response | Boolean option to return the full HTTP response including status code and headers instead of just the response body. |
Output
The node outputs the response from the Basecamp API after attempting to delete the specified message type. By default, it returns only the response body, which typically will be empty or contain confirmation of deletion. If "Return Full Response" is enabled, the output includes the full HTTP response object with status code, headers, and body, allowing for more detailed handling or debugging.
No binary data is involved in this operation.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication.
- The node expects the user to provide valid project and message type IDs.
- Proper API permissions are necessary to delete message types within the specified project.
Troubleshooting
- Invalid IDs: Providing incorrect or non-existent project or message type IDs will result in errors such as "Not Found" or "Unauthorized". Verify IDs before running the node.
- Insufficient Permissions: If the API credentials lack permission to delete message types, the node will fail with authorization errors. Ensure the connected account has appropriate rights.
- API Rate Limits: Frequent deletions may hit API rate limits; handle such errors by retrying after some delay.
- Return Full Response Confusion: Enabling "Return Full Response" changes the output format. Make sure downstream nodes expect this structure to avoid processing errors.
Links and References
- Basecamp API Documentation - Message Types
- n8n Documentation on HTTP Request Node (for understanding API interactions)