Actions64
- Instance Actions
- Chat Actions
- Message Actions
- Group Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
This node allows sending an image message through a messaging API by specifying the instance, recipient, and image data. It is useful for automating the delivery of images in chat or messaging platforms, such as sending product photos, event flyers, or visual updates directly to users or groups.
Typical use cases include:
- Sending promotional images to customers.
- Sharing screenshots or photos in support conversations.
- Broadcasting event images to group chats.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the messaging instance that will send the image message. |
| Recipient Number | The phone number or identifier of the message recipient. |
| Image | URL or base64 string representing the image to be sent. |
| Caption | Optional text caption to accompany the image. |
| Options | Additional settings for the message: |
| - Delay | Time in milliseconds to wait before sending the message (default 1200 ms). |
| - Reply to Message | ID of a message to which this image message should reply. |
| - Mentions | Settings to mention participants in the message: |
| -- Mention Everyone | Boolean flag to mention all participants in a group. |
| -- Numbers to Mention | Comma-separated list of specific numbers to mention if not mentioning everyone. |
Output
The node outputs a JSON array containing the response from the messaging API after attempting to send the image message. This typically includes metadata about the sent message such as message ID, status, timestamps, or error information if the send failed.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the Evolution API service.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The node uses HTTP requests to communicate with the Evolution API endpoint at
https://doc.evolution-api.com/api-reference.
Troubleshooting
- Unsupported operation error: If the node throws "Unsupported operation" it means the selected resource-operation combination is not implemented. Verify you have chosen "Message" as resource and "Send Image" as operation.
- Invalid recipient number: Ensure the recipient number is correctly formatted and registered on the messaging platform.
- Image format issues: The image must be accessible via URL or valid base64 string; otherwise, the API may reject the request.
- API authentication errors: Confirm that the API key or token credential is correctly set up and has permissions to send messages.
- Delay setting: Setting an excessively long delay might cause unexpected timing behavior; keep delays reasonable.
Links and References
- Evolution API Documentation (official API reference)
- n8n documentation on Creating Custom Nodes