Evolution API icon

Evolution API

Interact with Evolution API

Actions64

Overview

The node "Evolution API" allows interaction with the Evolution API service, specifically supporting various resources and operations. For the Message resource with the Send Status operation, it enables sending different types of status updates (text, image, video, audio) to contacts or all contacts in a messaging context. This is useful for automating status posts on messaging platforms where you want to broadcast updates, media, or announcements programmatically.

Practical examples:

  • Automatically posting a text status update to all contacts when a system event occurs.
  • Sending an image or video status with a caption to a selected list of contacts.
  • Broadcasting audio status messages during special campaigns or alerts.

Properties

Name Meaning
Name Da Instância The name of the instance that will send the status.
Status Type The type of status to post. Options: Text Status, Image Status, Video Status, Audio Status.
Content or URL The content or URL of the image, video, or audio to be posted. Required for media statuses.
Texto Para Image Status/Video Text caption for Image or Video status posts. Optional.
Cor Do Background Background color for the status (hex color code).
Text Font Font type for the text status. Options: SERIF, NORICAN REGULAR, BRYNDAN WRITE, BEBASNEUE REGULAR, OSWALD HEAVY.
Send to All Boolean flag indicating whether to send the status to all contacts.
Contact List Comma-separated list of contacts who will receive the status (used if "Send to All" is false).

Output

The node outputs a JSON array containing the result of the status sending operation. Each item in the output corresponds to the response from the Evolution API after attempting to send the status. The exact structure depends on the API response but generally includes confirmation of success or failure per contact or overall.

If binary data were involved (e.g., uploading media), it would be handled accordingly, but based on the provided properties and code, the output focuses on JSON responses confirming the status post.

Dependencies

  • Requires an API key credential for authenticating with the Evolution API.
  • The base URL for requests is https://doc.evolution-api.com/api-reference.
  • No other external dependencies are indicated.
  • Proper configuration of the API credential in n8n is necessary.

Troubleshooting

  • Common issues:

    • Missing required fields such as "Name Da Instância", "Content or URL" (for media), or "Contact List" when not sending to all.
    • Invalid URLs or unsupported media formats may cause the API to reject the request.
    • Network or authentication errors if the API key is invalid or missing.

  • Error messages:

    • "Operação não suportada." indicates the requested operation is not supported by the node; ensure correct Resource and Operation selections.
    • API errors returned from the Evolution API will be passed through; check the API documentation for error codes and meanings.

  • Resolutions:

    • Verify all required parameters are correctly filled.
    • Confirm the API key credential is valid and has proper permissions.
    • Check network connectivity and endpoint availability.

Links and References

Discussion