Actions48
- Custom Variable Actions
- Custom Variable Group Actions
- Event Actions
- Integration Actions
- Lead Actions
- Lead List Actions
Overview
This node is designed to send event data related to an "Order Refunded" operation within an e-commerce or order management context. It captures detailed customer and order information when an order refund event occurs, allowing workflows to react to refunds by triggering notifications, updating databases, or integrating with other systems.
Common scenarios include:
- Notifying customers or support teams about refunded orders.
- Updating CRM or ERP systems with refund details.
- Triggering follow-up actions such as restocking inventory or issuing credits.
Practical example:
When a customer requests a refund, this node can be used to send the refund event data including customer details, order totals, products involved, and delivery info to an external system for processing or record-keeping.
Properties
| Name | Meaning |
|---|---|
| First Name | Customer’s first name |
| Last Name | Customer’s last name |
| Phone | Customer phone number including country and area code |
| Customer’s email address | |
| Birth Date | Customer’s birth date (format: YYYY-MM-DD) |
| Gender | Customer’s gender |
| Tax ID (CPF/CNPJ) | Customer’s tax document identifier |
| IP Address | Customer’s IP address |
| Currency | Currency used by the customer (e.g., BRL, USD, GBP) |
| Order ID | Unique identifier of the refunded order |
| Products | List of products in the order, each with name, quantity, and value |
| Order Products Total Value | Sum of the values of all products in the order |
| Order Total Value | Total amount of the order after discounts |
| Discount | Total discount amount applied to the order |
| Status | Current order status description for enrichment |
| Address Parameters | Customer's address details including city, complement, country, neighborhood, number, postal code, state, street |
| Delivery Parameters | Delivery-related information including description, fee amount, message, tracking code, tracking URL, and estimated delivery date |
Output
The node outputs JSON data representing the event payload sent to the external service. This includes structured customer information, order details, product lists, and delivery data. The output reflects the successful transmission of the refund event data.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating HTTP requests to the external notification service at
https://api.notificacoesinteligentes.com. - The node uses an HTTP request helper method configured with authentication to send event data.
- Network connectivity to the external API endpoint is necessary.
Troubleshooting
Common issues:
- Missing required fields such as customer first name, phone, or order ID may cause the API to reject the event.
- Incorrect date formats for birthdate or estimated delivery date could lead to errors.
- Network timeouts or authentication failures if the API key is invalid or missing.
Error messages:
- Timeout errors indicate network or server unavailability; retry or check connectivity.
- Authentication errors suggest invalid or missing API credentials; verify and update credentials.
- Validation errors from the API usually specify which required field is missing or malformed; ensure all required properties are correctly set.
Links and References
- Notificações Inteligentes API Documentation (assumed base URL)
- n8n documentation on creating custom nodes and using HTTP Request with authentication
Note: The summary is based solely on static analysis of the provided property definitions and bundled source code snippet. The actual execute() method implementation was not included but inferred from the property routing and node description.