Actions114
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
- Call Actions
- Label Actions
- OpenAI Actions
- N8N Integration Actions
- EvoAI Actions
- Template Actions
- Business Actions
Message → Send List
AI-generatedOverview
This node sends a list message using the Evolution API. It is useful for scenarios where you want to send interactive list messages to recipients, such as menus or options in chat applications. For example, a business can send a product catalog or service options as a list to a customer via a messaging platform.
Use Case Examples
- Sending a list of product categories to a customer for easy selection.
- Sending a menu of service options in a customer support chat.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the instance that will send the list, used to identify the sending source. |
| Recipient Number | The phone number or identifier of the message recipient. |
| List Title | The main title of the list message, summarizing the list content. |
| Description | A description providing additional context or details about the list. |
| Button Text | The text displayed on the button that opens the list options. |
| Footer Text | Text shown in the footer area of the list message. |
| Sections | Sections of the list, each containing a title and multiple rows representing selectable options. Each row has a title, optional description, and a unique row ID. |
| Options | Additional message options such as delay before sending, message to reply to, and mentions settings (mention everyone or specific numbers). |
Output
JSON
messageId- The unique identifier of the sent list message.status- The status of the message sending operation (e.g., success or failure).
Dependencies
- Evolution API credentials for authentication
Troubleshooting
- Ensure all required fields (Instance Name, Recipient Number, List Title, Description, Button Text, Footer Text, and Sections) are provided and correctly formatted.
- Check that the Evolution API credentials are valid and have the necessary permissions.
- If the message fails to send, verify the recipient number format and network connectivity.
- Common error messages may include unsupported operation errors if the resource or operation names are incorrect, or API errors related to authentication or payload formatting.