Basecamp icon

Basecamp

Interact with Basecamp API

Actions76

Overview

This node interacts with the Basecamp API, specifically allowing users to delete a chatbot integration within a given project and chat. The "Delete a Chatbot" operation under the "Chatbot" resource removes an existing chatbot/integration from a specified chat (campfire) inside a project (bucket). This is useful for managing and cleaning up chatbot integrations that are no longer needed or relevant.

Practical examples include:

  • Removing outdated or deprecated chatbot integrations from a project’s chat.
  • Automating cleanup of chatbot resources when projects or chats are archived or deleted.
  • Managing chatbot lifecycle programmatically as part of a larger workflow.

Properties

Name Meaning
Project ID The ID of the project (bucket) where the chatbot exists; used in the API endpoint path.
chatId The ID of the chat/campfire within the project; used in the API endpoint path.
integrationId The ID of the chatbot/integration to be deleted; used in the API endpoint path.
Return Full Response Boolean flag indicating whether to return the full HTTP response (status code, headers, body) or just the response body.

Output

The node outputs JSON data representing the response from the Basecamp API after attempting to delete the chatbot integration. If "Return Full Response" is set to true, the output includes the full HTTP response details such as status code, headers, and body. Otherwise, only the response body is returned.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the Basecamp API using OAuth2 authentication with appropriate permissions to manage chatbots.
  • The node expects the Basecamp account ID to be configured in credentials to construct the API base URL.
  • No additional external dependencies beyond the Basecamp API and its authentication are required.

Troubleshooting

  • Common issues:

    • Invalid or missing IDs (Project ID, chatId, integrationId) will cause the API call to fail. Ensure all IDs correspond to existing resources.
    • Insufficient permissions or expired authentication tokens can result in authorization errors.
    • Network connectivity problems may prevent successful API communication.
  • Error messages:

    • 404 Not Found: The specified project, chat, or chatbot integration does not exist. Verify the IDs.
    • 401 Unauthorized / 403 Forbidden: Authentication failed or insufficient permissions. Refresh credentials or check access rights.
    • 400 Bad Request: Malformed request, possibly due to invalid parameter types or missing required fields.

Resolving these typically involves verifying input parameters, refreshing or reconfiguring credentials, and ensuring the user has the necessary permissions in Basecamp.

Links and References

Discussion