Actions64
- Instance Actions
- Message Actions
- Group Actions
- Integration Actions
- Chat Actions
- Profile Actions
- Event Actions
Overview
The node provides functionality to send an image message through a messaging API associated with the "Evolution API" service. It allows users to specify the instance sending the message, the recipient's number, and the image content either as a URL or base64 string. Additional options include adding a caption, setting a delay before sending, replying to a specific message, and mentioning participants in a group chat.
This node is beneficial in scenarios such as:
- Automating customer support by sending product images or instructions.
- Broadcasting promotional images to multiple recipients.
- Replying to user queries with relevant images while referencing previous messages.
- Sending images with mentions to notify specific users or everyone in a group.
Example use case: A business wants to automatically send a welcome image with a caption to new customers who sign up, optionally tagging their account manager.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the instance that will send the message. |
| Recipient Number | The phone number or identifier of the message recipient. |
| Image | The image to send, provided as a URL or a base64 encoded string. |
| Caption | Optional text to accompany the image message. |
| Options | Collection of additional settings: |
| - Delay | Time in milliseconds to wait before sending the message (default 1200 ms). |
| - Reply Message | ID of a message to reply to, enabling threaded conversations. |
| - Mentions | Settings for mentioning participants: |
| -- Mention Everyone | Boolean flag to mention all participants in a group. |
| -- Numbers To Mention | Comma-separated list of specific numbers to mention (used if not mentioning everyone). |
Output
The node outputs a JSON array containing the result of the send image operation. This typically includes confirmation details such as message IDs, status, timestamps, or any metadata returned by the Evolution API after sending the image message.
If the node supports binary data output (not explicitly shown in the code), it would represent media content or attachments related to the message.
Dependencies
- Requires an active connection to the Evolution API service.
- Needs an API authentication credential configured in n8n to authorize requests.
- The base URL for API requests is set to
https://doc.evolution-api.com/api-reference. - No other external dependencies are indicated.
Troubleshooting
- Operation Not Supported Error: If the specified resource or operation is not implemented, the node throws an error stating the function is unsupported. Ensure the resource is "messages-api" and operation is "send-image".
- Missing Required Parameters: The node requires instance name, recipient number, and image data. Omitting these will likely cause errors.
- Invalid Image Format: Providing an invalid URL or malformed base64 string may cause the API to reject the message.
- API Authentication Failures: Incorrect or missing API credentials will prevent successful message sending.
- Delay Misconfiguration: Setting an excessively long delay might cause unexpected timing issues.
To resolve errors, verify all required fields are correctly filled, check API credentials, and ensure the image data is valid.
Links and References
- Evolution API Documentation (base URL used in the node)
- n8n Documentation on Creating Custom Nodes