Actions64
- Instance Actions
- Chat Actions
- Message Actions
- Group Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
The node "Evolution API" provides an interface to interact with the Evolution API, specifically supporting various resources and operations. For the Message resource with the Send PIX operation, it enables sending a PIX payment message to a specified recipient. This is useful in scenarios where automated financial transactions or payment requests need to be sent programmatically via the Evolution API.
Practical examples include:
- Sending a PIX payment request to a customer after an online purchase.
- Automating payroll or vendor payments using PIX keys.
- Integrating PIX payment notifications into business workflows.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the instance that will send the PIX payment message. |
| Recipient Number | The identifier (likely phone number or chat ID) of the recipient who will receive the PIX. |
| Beneficiary Name | The full name of the PIX beneficiary receiving the payment. |
| Key Type | The type of PIX key used for the transaction. Options: Phone, E-Mail, CPF, CNPJ, Random. |
| PIX Key | The actual PIX key string corresponding to the beneficiary's account. |
Output
The node outputs a JSON array containing the response from the Evolution API after attempting to send the PIX message. The exact structure depends on the API response but typically includes confirmation details such as status, transaction ID, or error messages if any.
No binary data output is indicated by the source code.
Dependencies
- Requires an active connection to the Evolution API service.
- Needs an API authentication credential configured in n8n (an API key or token).
- The base URL for the API is
https://doc.evolution-api.com/api-reference. - The node expects JSON content-type headers for requests and responses.
Troubleshooting
- Unsupported operation error: If the node throws an error about unsupported operation, verify that the Resource is set to "messages-api" and Operation to "send-pix".
- Missing required parameters: Ensure all required properties (Instance Name, Recipient Number, Beneficiary Name, Key Type, PIX Key) are provided and correctly formatted.
- API authentication errors: Confirm that the API credentials are valid and have sufficient permissions.
- Network or connectivity issues: Check internet access and API endpoint availability.
- Invalid PIX key or key type: Validate that the PIX key matches the selected key type (e.g., phone number format for Phone, valid CPF/CNPJ format).
Links and References
- Evolution API Documentation
- PIX Payment System Overview (Central Bank of Brazil)
Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.