Actions80
- 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
- Todos Actions
Overview
This node operation, Destroy Chatbot, is designed to delete a specific chatbot within a given environment. It targets chatbots associated with particular buckets and integrations, allowing users to programmatically remove chatbots that are no longer needed or relevant.
Common scenarios for this operation include:
- Cleaning up obsolete or test chatbots from a system.
- Automating chatbot lifecycle management by removing bots when certain conditions are met.
- Managing chatbot resources in bulk via workflows.
For example, if you have multiple chatbots deployed across different projects or teams, you can use this operation to delete a chatbot by specifying its bucket, chat, and integration identifiers.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | Numeric identifier of the bucket where the chatbot resides. |
| Chat Id | Numeric identifier of the specific chat instance associated with the chatbot. |
| Integration Id | Numeric identifier of the integration linked to the chatbot to be destroyed. |
Output
The output of this operation typically contains a JSON object reflecting the result of the deletion request. This may include confirmation of successful deletion or details about the removed chatbot. The exact structure depends on the API response but generally confirms whether the chatbot was destroyed.
No binary data output is expected from this operation.
Dependencies
- Requires an active connection to the Basecamp API (or equivalent service managing chatbots).
- Needs proper authentication credentials configured in n8n to authorize API requests.
- The node uses HTTP headers to accept and send JSON-formatted data.
- The base URL for API requests is dynamically constructed using the authenticated user's account information.
Troubleshooting
- Invalid or missing IDs: Ensure that the Bucket Id, Chat Id, and Integration Id are correct and correspond to existing resources; otherwise, the API will return errors indicating resource not found.
- Authentication errors: Verify that the API key or OAuth token is valid and has sufficient permissions to delete chatbots.
- Network issues: Check connectivity to the API endpoint and ensure no firewall or proxy is blocking requests.
- API rate limits: If many deletions are performed rapidly, the API might throttle requests; implement retries or delays as needed.
Common error messages might include:
- "Resource not found" — check the provided IDs.
- "Unauthorized" — verify credentials.
- "Bad Request" — confirm all required parameters are correctly formatted.
Links and References
- Basecamp API Documentation (for general API reference)
- n8n documentation on HTTP Request Node for understanding how API calls are made within nodes.