Actions64
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
- Instancia Actions
- Mensagem Actions
- Grupo Actions
Overview
This node integrates with the Typebot service via the Evolution API, enabling users to manage and interact with Typebot chatbots programmatically. It supports operations such as creating, updating, deleting, starting Typebots, managing sessions, and changing session statuses.
Common scenarios include automating chatbot lifecycle management, triggering chatbots based on keywords or other triggers, monitoring active sessions, and controlling chatbot behavior dynamically within workflows.
Practical examples:
- Automatically create a new Typebot flow when launching a new campaign.
- Start a Typebot session for a specific user based on an incoming message.
- Fetch all active sessions to analyze chatbot engagement.
- Pause or close a chatbot session based on external events.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instancia | The name of the instance that will send the message. |
| O Que Deseja Fazer | Operation to perform with the Typebot integration. Options: Add Typebot, Verify Typebot, Update Typebot, Delete Typebot, Start Typebot, Search Session in Typebot, Change Session Status in Typebot. |
| ID Do Typebot | The ID of the Typebot to target. Leave empty to fetch all (used in find, update, delete, fetch sessions, change status operations). |
| URL Da API Do Typebot | The URL of your Typebot API endpoint (required for create, update, start operations). |
| Nome Do Typebot | The name of your Typebot flow (required for create, update, start operations). |
| Tipo De Gatilho | Trigger type for the Typebot: Keyword or All (required for create, update). |
| Operador Do Gatilho | Trigger operator when using keyword trigger: Contains, Equals, Starts With, Ends With, Regex (required for create, update). |
| Gatilho | The keyword, phrase, or regex used as a trigger to start the Typebot (required for create, update with keyword trigger). |
| Expira Em (Minutos) | Number of minutes without response after which the bot should be deactivated (required for create, update). |
| Palavra Chave De Finalização | Keyword or phrase used to close the bot session (required for create, update). |
| Delay Padrão Da Mensagem | Default delay in milliseconds before sending a message from the bot (required for create, update). |
| Palavra Chave De Finalização | Message shown when input is not recognized by the bot (required for create, update). |
| Escuta Mensagens Enviadas Por Mim | Whether the bot listens to messages sent by the user themselves (boolean, create, update). |
| Pausa O Bot Quando Eu Enviar Uma Mensagem | Whether to pause the bot when the user sends a message (boolean, create, update). |
| Mantem a Sessão Do Bot Aberta | Whether to keep the bot session open (boolean, create, update). |
| Tempo De Espera (Em Segundos) | Time in seconds the bot waits for additional messages before processing them together (debounce time) (required for create, update). |
| Numero Do Destinatario | RemoteJid of the recipient (required for start and change status operations). |
| Iniciar Seção | Whether to start a new session when starting the Typebot (boolean, start operation). |
| Variáveis | Variables to send to the Typebot as key-value pairs (start operation). |
| Status | Status to set for the session: Opened, Paused, Closed (change status operation). |
Output
The node outputs JSON data representing the result of the performed operation. This typically includes details about the Typebot instance, session information, or confirmation of actions like creation, update, deletion, or status changes.
If applicable, the output may contain arrays of sessions or objects describing the current state of a Typebot or its sessions.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The user must provide the correct Typebot API URL and relevant parameters.
- No other external dependencies are explicitly required.
Troubleshooting
- Operation Not Supported Error: If an unsupported operation is selected, the node throws an error indicating the operation is not supported. Ensure the chosen operation matches one of the available options.
- Missing Required Parameters: Operations require certain parameters (e.g., Typebot ID, URL, or remoteJid). Missing these will cause errors. Double-check required fields per operation.
- API Connectivity Issues: Incorrect API URLs or invalid credentials can cause connection failures. Verify the API endpoint and authentication token.
- Invalid Trigger Configuration: When using keyword triggers, ensure the trigger value and operator are correctly set; otherwise, the Typebot may not activate as expected.
- Session Management Errors: Changing session status or fetching sessions requires valid Typebot IDs and session identifiers. Confirm these values before executing.
Links and References
- Typebot Official Documentation
- Evolution API Documentation (replace with actual URL if known)
- n8n Documentation on Creating Custom Nodes