Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
This node integrates with the Evolution API to manage Chatwoot settings and status within an automation workflow. It allows users to enable or disable Chatwoot integration, verify its current state, and configure various Chatwoot-related options such as importing contacts and messages, managing inboxes, and setting conversation behaviors.
Common scenarios include:
- Automating the activation or deactivation of Chatwoot integration for a given instance.
- Checking if Chatwoot is currently enabled or configured properly.
- Importing historical contacts and messages into Chatwoot automatically.
- Customizing how conversations are handled in Chatwoot (e.g., reopening messages, starting conversations as pending).
- Managing Chatwoot inboxes and agent signatures programmatically.
Practical example:
- A customer support team wants to automate enabling Chatwoot integration when launching a new instance, import recent chat history, and ensure all conversations start as pending for better tracking.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instancia | The name of the instance that will send the message. |
| O Que Deseja Fazer | Choose between activating/deactivating Chatwoot ("Definir Chatwoot") or verifying Chatwoot ("Verificar Chatwoot"). |
| Ativar Chatwoot | Enable or disable integration with Chatwoot (boolean). |
| Link Do Chatwoot | URL link to the Chatwoot instance. |
| ID Da Conta Do Chatwoot | Account ID for the Chatwoot instance. |
| Token De Admin Do Chatwoot | Admin token for authenticating with Chatwoot (password type). |
| Assinatura Do Agente Do Chatwoot | Enable or disable the Chatwoot agent signature on messages (boolean). |
| Reabrir Mensagens No Chatwoot | Enable or disable reopening messages in Chatwoot (boolean). |
| Iniciar Conversas Como Pendentes No Chatwoot | Start conversations as pending in Chatwoot (boolean). |
| Importar Contatos Para O Chatwoot | Enable or disable importing contacts into Chatwoot (boolean). |
| Nome Da Inbox Do Chatwoot | Optional: Name of the Chatwoot inbox. |
| Mesclar Contatos Brasileiros No Chatwoot | Enable or disable merging Brazilian contacts in Chatwoot (boolean). |
| Importar Mensagens Para O Chatwoot | Enable or disable importing messages into Chatwoot (boolean). |
| Importar Mensagens De Quantos Dias Para O Chatwoot | Optional: Number of days to limit message import into Chatwoot (number). |
| Criar Caixa De Entrada | Enable or disable automatic creation of inbox (boolean). |
| Nome Do Contato De QRCode No Chatwoot | Optional: Name of the QR code contact in Chatwoot. |
| Url Do Logo Para O Contato No Chatwoot | Optional: URL of the logo image for the contact in Chatwoot. |
Output
The node outputs a JSON array containing the result of the requested operation related to Chatwoot integration. This typically includes confirmation of the action performed (e.g., success status), details about the Chatwoot configuration, or verification results depending on the chosen operation.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- Needs valid Chatwoot account credentials including admin token, account ID, and Chatwoot URL.
- The node expects proper configuration of these credentials within n8n to communicate securely with both Evolution API and Chatwoot services.
Troubleshooting
Common issues:
- Missing or incorrect Chatwoot URL, account ID, or admin token will cause authentication failures.
- Selecting unsupported operations or resources will throw errors indicating unsupported functions.
- Network connectivity problems may prevent communication with the Evolution API or Chatwoot endpoints.
Error messages:
"Operação não suportada."means the selected operation is not supported for the resource; verify the operation and resource names.- Authentication errors usually indicate invalid or missing tokens; ensure credentials are correctly set.
- Validation errors may occur if required fields like instance name or Chatwoot URL are empty.
Resolutions:
- Double-check all required input properties for correctness and completeness.
- Ensure API keys and tokens have appropriate permissions.
- Verify network access to the specified Chatwoot URL.
Links and References
- Chatwoot Official Documentation
- Evolution API Reference (base URL used by the node)
- n8n Documentation on Creating Custom Nodes