N8N Tools - Typebot API icon

N8N Tools - Typebot API

Complete Typebot.io integration - Self-hosted chatbot builder with visual flows

Actions23

Overview

This node provides a comprehensive integration with Typebot.io, a self-hosted chatbot builder platform that uses visual flows to create chatbots. The node allows managing typebots (chatbots), chat sessions, conversation results, and workspace settings through various operations.

The Delete Typebot operation specifically deletes an existing typebot by its ID. This is useful when you want to remove obsolete or unwanted chatbots from your workspace programmatically.

Practical scenarios include:

  • Automating cleanup of test or deprecated chatbots.
  • Managing chatbot lifecycle in CI/CD pipelines.
  • Integrating chatbot management into broader workflow automation.

Properties

Name Meaning
Typebot ID The unique identifier of the typebot to delete.
Additional Fields Not used for Delete Typebot operation; available for other operations.

Output

The output is a JSON object representing the response from the Typebot API after attempting to delete the specified typebot. Typically, this will confirm successful deletion or provide error details if the operation failed.

Example output structure:

{
  "json": {
    // API response confirming deletion or error message
  },
  "pairedItem": {
    "item": 0
  }
}

No binary data is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Typebot API.
  • Needs configuration of the Typebot API URL and authentication token within n8n credentials.
  • The node sends HTTP requests to the Typebot API endpoints.

Troubleshooting

  • Common issues:

    • Invalid or missing Typebot ID will cause the API to reject the request.
    • Insufficient permissions or invalid API token may result in authorization errors.
    • Network connectivity problems can prevent reaching the Typebot API.

  • Error messages:

    • "Unknown typebot operation: deleteTypebot": Indicates a misconfiguration or typo in the operation name.
    • API errors returned in the JSON response will be passed through; check the message for details.

  • Resolutions:

    • Verify the Typebot ID is correct and exists.
    • Ensure the API token and credentials are valid and have necessary permissions.
    • Check network access to the configured API URL.
    • Enable "Continue On Fail" in the node settings to handle errors gracefully in workflows.

Links and References

Discussion