Evolution API

Interact with Evolution API

Actions64

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 a Typebot instance, fetching sessions, and changing session statuses.

Typical use cases include automating chatbot lifecycle management, triggering bots based on keywords or other triggers, monitoring active sessions, and controlling bot behavior dynamically within an n8n workflow.

For example, you can create a new Typebot configured with specific trigger keywords, start it for a particular recipient, or pause/resume sessions 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: Adicionar Typebot (create), Verificar Typebot (find), Atualizar Typebot (update), Deletar Typebot (delete), Iniciar Typebot (start), Procurar Sessão (fetch sessions), Alterar Status Da Sessão (change status).
ID Do Typebot	The ID of the Typebot to target. Leave empty to fetch all. Required for find, update, delete, fetch sessions, and change status operations.
URL Da API Do Typebot	The URL of your Typebot API endpoint. Required for create, update, and start operations.
Nome Do Typebot	The name of your Typebot flow. Required for create, update, and start operations.
Tipo De Gatilho	Trigger type for the Typebot. Options: Palavra Chave (keyword), Todos (all). Used in create and update operations.
Operador Do Gatilho	Trigger operator when using keyword trigger type. Options: Contem (contains), Igual À (equals), Começa com (startsWith), Termina com (endsWith), Regex (regex). Used in create and update operations.
Gatilho	The word/phrase or regex used as a trigger to start the Typebot. Required when trigger type is keyword.
Expira Em (Minutos)	Number of minutes without response after which the bot should be deactivated. Required for create and update.
Palavra Chave De Finalização	Keyword or phrase used to close the bot session. Required for create and update.
Delay Padrão Da Mensagem	Default delay in milliseconds before sending a message from the bot. Required for create and update.
Palavra Chave De Finalização	Message shown when input is not recognized by the bot. Required for create and update.
Escuta Mensagens Enviadas Por Mim	Boolean indicating whether the bot listens to messages sent by the user themselves.
Pausa O Bot Quando Eu Enviar Uma Mensagem	Boolean indicating whether the bot pauses when the user sends a message.
Mantem a Sessão Do Bot Aberta	Boolean indicating whether to keep the bot session open.
Tempo De Espera (Em Segundos)	Time in seconds the bot waits for additional messages after receiving one, then concatenates them into a single message. Required for create and update.
Numero Do Destinatario	RemoteJid (recipient identifier) for whom the bot session is started or whose session status is changed. Required for start and change status operations.
Iniciar Seção	Boolean to indicate whether to start a new session when starting the Typebot. Used in start operation.
Variáveis	Collection of variables (name-value pairs) to send to the Typebot when starting it. Used in start operation.
Status	Status to set for a session. Options: Aberta (opened), Pausada (paused), Fechada (closed). Used in change status operation.

Output

The node outputs JSON data representing the result of the requested operation. This typically includes details about the Typebot instance, session information, or confirmation of actions performed (e.g., creation success, updated status).

The exact structure depends on the operation:

For creation or update, it returns the created/updated Typebot details.
For fetching, it returns one or more Typebot instances or sessions.
For starting or changing status, it returns confirmation and current session state.

No binary data output is indicated.

Dependencies

Requires an API key credential for authenticating with the Evolution API.
The node expects the base URL and endpoints related to the Evolution API.
Proper configuration of the Typebot API URL and credentials is necessary.
No other external dependencies are indicated.

Troubleshooting

Operation Not Supported Error: If an unsupported operation or resource is selected, the node throws an error indicating the function is not supported. Ensure the correct Resource ("integrations-api") and Operation ("typebot") are chosen.
Missing Required Parameters: Operations require certain parameters like instanceName, url, typebot, or remoteJid. Missing these will cause errors. Double-check required fields per operation.
API Connectivity Issues: Errors connecting to the Typebot API may occur if the URL or credentials are incorrect. Verify API endpoint URLs and authentication tokens.
Invalid Trigger Configuration: When using keyword triggers, ensure the trigger value and operator are correctly set; invalid regex or empty triggers may cause failures.
Session Management Errors: Changing session status or fetching sessions requires valid Typebot IDs and session identifiers; invalid IDs will lead to errors.