Actions64
- Instance Actions
- Message Actions
- Group Actions
- Integration Actions
- Chat Actions
- Profile Actions
- Event Actions
Overview
The "Send Status" operation of the Message resource in this node allows users to post various types of status updates through an instance of a messaging platform. This includes text statuses, as well as multimedia statuses such as images, videos, and audio clips. The node supports sending these statuses either to all contacts or to a specified list of contacts.
This functionality is useful for automating status updates in messaging apps, broadcasting announcements, sharing media content with selected recipients, or maintaining active engagement with contacts by regularly updating status messages.
Practical examples:
- Posting a text announcement to all contacts about a new product launch.
- Sharing an image or video status with a specific group of contacts.
- Sending an audio message as a status update to select contacts.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the messaging 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 text or URL pointing to the image, video, or audio file to be posted as status. |
| Text For Image/Video Status | Optional caption text accompanying image or video statuses. |
| Background Color | Background color for the status (applicable mainly for text statuses). |
| Text Font | Font style for the text in the status. Options include 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 to receive the status (required if not sending to all contacts). |
Output
The node outputs a JSON array containing the result of the status posting operation. Each item in the output corresponds to the response from the API after attempting to send the status. The exact structure depends on the Evolution API's response but typically includes confirmation of success or failure and any relevant metadata.
If the status includes multimedia content, the node handles URLs or references to those files but does not output binary data directly.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node configuration must include valid credentials to access the Evolution API endpoint.
- Network connectivity to the Evolution API service at
https://doc.evolution-api.com/api-reference.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Incorrect or empty required fields like "Instance Name," "Content Or URL," or "Contact List" (when not sending to all) will result in errors.
- Providing an unsupported status type or malformed contact list may cause the API to reject the request.
Error messages:
"Operation not supported."— indicates the requested operation is not implemented; verify the operation and resource names.- API errors related to invalid parameters or authentication will be returned from the Evolution API and surfaced by the node; check credentials and input values.
Resolution tips:
- Ensure all required properties are correctly filled.
- Validate the format of the contact list (comma-separated).
- Confirm that the API credentials are current and have necessary permissions.
- Review the Evolution API documentation for any constraints on content types or sizes.
Links and References
- Evolution API Documentation (official API reference for detailed endpoint behavior and parameters)