Actions80
- Todos Actions
- Card Tables Actions
- Forwards Actions
- Events Actions
- Recordings Actions
- Projects Actions
- People Actions
- Chatbots Actions
- Webhooks Actions
- Attachments Actions
- Templates Actions
- Uploads Actions
- Documents Actions
- Lineup Markers Actions
- Subscriptions Actions
- Schedules Actions
- Schedule Entries Actions
- Todo Sets Actions
- Todo Lists Actions
Overview
This node operation allows you to delete (destroy) a specific chatbot within a Basecamp environment. It is useful when you want to programmatically remove chatbots that are no longer needed or to clean up resources automatically as part of workflow automation.
Practical examples include:
- Automatically removing chatbots associated with completed projects.
- Cleaning up test chatbots created during development.
- Managing chatbot lifecycle by deleting outdated or inactive bots.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The unique identifier of the bucket (project area) where the chatbot resides. |
| Chat Id | The unique identifier of the chat associated with the chatbot to be destroyed. |
| Integration Id | The unique identifier of the integration (chatbot) that you want to delete. |
Output
The output JSON will typically contain the response from the API confirming the deletion of the chatbot. This may include status information or confirmation messages indicating successful removal.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node uses the Basecamp API endpoint, which requires the Basecamp account ID to construct the base URL.
- Proper permissions on the Basecamp account to delete chatbots are necessary.
Troubleshooting
Common issues:
- Invalid or missing identifiers (Bucket Id, Chat Id, Integration Id) will cause the operation to fail.
- Insufficient permissions or invalid API credentials can result in authorization errors.
- Network connectivity problems may prevent reaching the Basecamp API.
Error messages and resolutions:
- "Unauthorized" or "Forbidden": Check that the API key credential is valid and has sufficient permissions.
- "Not Found": Verify that the Bucket Id, Chat Id, and Integration Id are correct and correspond to existing resources.
- "Bad Request": Ensure all required parameters are provided and correctly formatted.