Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The node "Evolution API" allows users to interact with the Evolution API service, specifically enabling sending status updates (stories) through a messaging platform. The "Enviar Status" operation under the "Mensagem" resource lets users post different types of status updates such as text, image, video, or audio to contacts or all contacts in their instance.
This node is beneficial for automating status updates in messaging workflows, for example:
- Broadcasting announcements or promotions via text status.
- Sharing multimedia content like images or videos as status updates.
- Sending audio clips as status messages to selected contacts or all contacts.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance that will send the status update. |
| Tipo Do Status | The type of status to post. Options: Status De Texto (text), Status De Imagem (image), Status De Video (video), Status De Audio (audio). |
| Conteudo Ou URL | The content or URL of the image/video/audio to be posted. Required for all types. |
| Texto Para Status De Imagem/Video | Text caption for image or video status types. Optional. |
| Cor Do Background | Background color for the status (hex color code). Default is black (#000000). |
| Font Do Texto | Font type for the text. Options: SERIF, NORICAN REGULAR, BRYNDAN WRITE, BEBASNEUE REGULAR, OSWALD HEAVY. |
| Enviar Para Todos | Boolean flag indicating whether to send the status to all contacts. |
| Lista De Contatos | Comma-separated list of contacts who will receive the status. Required if not sending to all. |
Output
The node outputs a JSON array containing the response from the Evolution API after attempting to send the status update. The exact structure depends on the API response but generally includes confirmation of the sent status or error details.
If the status involves media (image, video, audio), the node handles URLs pointing to these resources; however, it does not output binary data directly.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node expects the Evolution API base URL and headers to be configured internally.
- No additional external dependencies are indicated beyond the Evolution API service.
Troubleshooting
Common issues:
- Missing required fields such as instance name, content/URL, or contact list when not sending to all.
- Invalid URLs for media content may cause failures in posting statuses.
- Incorrect font or color values might not throw errors but could affect appearance.
- Network or authentication errors if the API key is invalid or missing.
Error messages:
- "Operação não suportada." indicates an unsupported operation-resource combination was requested.
- API errors returned by the Evolution API will be passed through; check the message for details.
Resolutions:
- Ensure all required properties are correctly filled.
- Validate URLs before use.
- Confirm API credentials are set up properly in n8n.
- Use the built-in test button to verify connectivity and basic functionality.
Links and References
- Evolution API Documentation (as referenced in the node's base URL)
- n8n documentation on creating and using custom nodes for API integrations