Actions23
- Typebot Actions
- Chat Actions
- Result Actions
- Workspace Actions
Overview
The "Import Typebot" operation in this node allows users to import a Typebot chatbot configuration into their workspace on the Typebot.io platform. This is useful for automating the deployment or updating of chatbots by importing their JSON configurations programmatically.
Typical scenarios include:
- Migrating or restoring a chatbot from a saved JSON configuration.
- Automating chatbot setup as part of CI/CD pipelines.
- Bulk importing multiple chatbots into a workspace.
For example, you might have a Typebot JSON export from another environment and want to import it into your current workspace with a new name using this node.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | Collection of optional fields to customize the import: |
| - Stream Enabled | Enable streaming for real-time responses (boolean) |
| - Prefilled Variables | Variables to prefill in the typebot; each variable has a name and value (multiple allowed) |
| - Result ID | Existing result ID to continue conversation (string) |
| - Theme | Custom theme configuration as JSON |
| - Settings | Custom settings as JSON |
| - Icon | Typebot icon, either an emoji or URL |
| - Typebot JSON | The actual Typebot configuration as JSON to import/update |
| - Export Format | Format for exporting results (CSV, JSON, Excel) — not relevant for import but part of collection |
| - Filename | Custom filename for file uploads (not directly relevant here) |
| - File Size Limit MB | File size limit in megabytes (not directly relevant here) |
Additional required properties for this operation (inherited from the node):
| Name | Meaning |
|---|---|
| Resource | Fixed to "Typebot" |
| Operation | Fixed to "Import Typebot" |
| Typebot Name | Name to assign to the imported Typebot |
Output
The output JSON contains the response from the Typebot API after attempting to import the Typebot configuration. It typically includes details about the newly created Typebot such as its ID, name, workspace association, and other metadata returned by the API.
If the import fails, the output will contain an error message describing the failure.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Typebot API.
- Needs the base API URL and an API token configured in the node credentials.
- Workspace ID must be set in credentials to associate the imported Typebot with the correct workspace.
- The node sends requests through a proxy service hosted at
https://n8ntools.io/api/v1/proxy/typebotwhich requires an additional API key for that proxy.
Troubleshooting
Common issues:
- Invalid or malformed JSON in the "Typebot JSON" field can cause import failures.
- Missing or incorrect API credentials will result in authentication errors.
- Providing a duplicate Typebot name may cause conflicts depending on the API behavior.
- Network or proxy issues could prevent successful API calls.
Error messages:
- Errors from the API are returned in the output JSON under an
errorfield if the node is set to continue on fail. - Authentication errors usually indicate invalid or missing API tokens.
- Validation errors often point to problems in the JSON configuration or missing required fields.
- Errors from the API are returned in the output JSON under an
Resolutions:
- Validate the JSON configuration before importing.
- Ensure all required credentials and workspace IDs are correctly configured.
- Check network connectivity and proxy API key validity.
- Use the node's "continue on fail" option to handle partial failures gracefully.