Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The node "Evolution API Direct" allows users to interact with the Evolution API by sending status updates (stories) directly via a specified server URL and API key. It supports posting different types of status content such as text, images, videos, and audio. This node is useful for automating status updates in messaging or social platforms that integrate with the Evolution API.
Typical use cases include:
- Automatically posting text or multimedia status updates to a messaging platform.
- Broadcasting status updates to all contacts or a selected list of contacts.
- Customizing the appearance of status posts with background colors and fonts.
For example, a marketing automation workflow could post promotional video statuses to a targeted contact list at scheduled intervals.
Properties
| Name | Meaning |
|---|---|
| Server URL | The full URL of your Evolution API server endpoint. |
| API Key | The API key credential for authenticating requests to the Evolution API instance. |
| 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: text, image, video, audio. |
| Conteudo Ou URL | The content text or URL of the media (image/video/audio) to be posted as status. |
| Texto Para Status De Imagem/Video | Caption text for image or video status posts. |
| Cor Do Background | Background color for the status post, specified as a hex color code (e.g., #000000). |
| Font Do Texto | Font style for the text in the status. Options: SERIF, NORICAN REGULAR, BRYNDAN WRITE, BEBASNEUE REGULAR, OSWALD HEAVY. |
| Enviar Para Todos | Boolean flag indicating whether to send the status to all contacts (true) or not (false). |
| Lista De Contatos | Comma-separated list of contact IDs to receive the status (used if "Enviar Para Todos" is false). |
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 typically includes confirmation details about the posted status.
If the status involves media (image, video, audio), the output may reference URLs or identifiers related to the uploaded content.
No binary data output is indicated by the source code.
Dependencies
- Requires access to an Evolution API server reachable via the provided Server URL.
- Requires a valid API key credential for authentication.
- No additional external dependencies are indicated.
- The node expects proper configuration of the API endpoint and credentials within n8n.
Troubleshooting
Common issues:
- Invalid or missing API key causing authentication failures.
- Incorrect Server URL leading to connection errors.
- Improperly formatted contact list or empty required fields causing request rejections.
- Unsupported operation or resource selection resulting in errors.
Error messages:
"Operação não suportada."indicates the chosen operation-resource combination is not implemented.- Network or HTTP errors from the API should be checked by verifying credentials and endpoint accessibility.
Resolutions:
- Double-check API key validity and permissions.
- Verify the Server URL is correct and accessible.
- Ensure required properties are filled and correctly formatted.
- Confirm the operation and resource names match supported values.
Links and References
- Evolution API Documentation (as referenced in the default baseURL)
- n8n documentation on Creating Custom Nodes