Basecamp icon

Basecamp

Interact with the Basecamp API

Actions80

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 were created by mistake, helping maintain a clean and organized workspace.

Practical examples include:

  • Automatically cleaning up test chatbots after development.
  • Removing obsolete chatbots as part of a workflow triggered by project changes.
  • Managing chatbot lifecycle in bulk via automation.

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 Basecamp API confirming the deletion of the chatbot. This may include status information or an empty object indicating success. No binary data is expected from this operation.

Dependencies

  • Requires an API key credential for authenticating with the Basecamp API.
  • The node uses the Basecamp API endpoint constructed dynamically based on the authenticated user's Basecamp ID.
  • Proper permissions to delete chatbots in the specified bucket and chat are necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Bucket Id, Chat Id, or Integration Id will cause the operation to fail.
    • Insufficient permissions or invalid API credentials can result in authorization errors.
    • Network connectivity problems may prevent successful API calls.
  • Error messages:

    • "Unauthorized" or "Forbidden": Check API credentials and user permissions.
    • "Not Found": Verify that the Bucket Id, Chat Id, and Integration Id are correct and exist.
    • "Bad Request": Ensure all required parameters are provided and valid.

Resolving these usually involves verifying input values, checking API credentials, and ensuring the user has appropriate access rights.

Links and References

Discussion