Actions48
- Custom Variable Actions
- Custom Variable Group Actions
- Event Actions
- Integration Actions
- Lead Actions
- Lead List Actions
Overview
The "Order Delivered" operation under the "Event" resource is designed to send detailed event data about an order delivery to an external system. This node captures comprehensive customer and order information, including personal details, products purchased, pricing, discounts, delivery specifics, and address data. It is useful for integrating e-commerce platforms or order management systems with notification services or analytics tools that track order lifecycle events.
Typical use cases include:
- Notifying a CRM or marketing platform when an order has been delivered.
- Triggering follow-up workflows such as sending thank-you emails or requesting feedback.
- Updating inventory or sales dashboards with real-time order delivery data.
For example, after an order is marked as delivered in your store, this node can send the customer's name, contact info, purchased products, total amounts, and delivery tracking details to a notification service to automate customer communication.
Properties
| Name | Meaning |
|---|---|
| ID | The ID of the existing integration (used internally, not relevant for this operation) |
| 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) |
| Products | List of products in the order; each product includes: Product Name, Quantity, and Value |
| Order ID | Unique identifier of the order |
| Order Products Total Value | Sum of the values of all products in the order |
| Order Total Value | Total amount of the order |
| Discount | Total discount applied to the order |
| Status | Current order status description |
| Address Parameters | Customer's address details including city, complement, country, neighborhood, number, postal code, state, street |
| Delivery Parameters | Delivery information including description, fee amount, message, tracking code, tracking URL, estimated delivery date |
Output
The node outputs JSON data representing the event sent to the external system. This JSON includes structured customer information, order details, product list, pricing, discounts, delivery data, and address fields as provided in the input properties.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating requests to the external notification service.
- The node uses HTTP requests to communicate with the external API endpoint at
https://api.notificacoesinteligentes.com. - Proper network connectivity and valid credentials are necessary for successful execution.
Troubleshooting
- Missing Required Fields: The node requires certain fields like First Name, Phone, Products, Order ID, and pricing details. Omitting these will likely cause errors or incomplete event submission.
- Invalid Date Format: The birthdate and estimated delivery date must be in the correct format (
YYYY-MM-DD). Incorrect formats may cause rejection by the API. - API Authentication Errors: Ensure the API key or authentication token is correctly configured in n8n credentials. Authentication failures will prevent event creation.
- Network Timeouts: The node sets a 5-second timeout on HTTP requests. Slow or unstable connections might cause timeouts.
- Product Data Structure: Products must be provided as an array of objects with name, quantity, and value. Improper formatting may lead to errors.
Links and References
- Notificações Inteligentes API Documentation (assumed base URL)
- General n8n documentation on creating custom nodes and using HTTP request credentials.
This summary is based solely on static analysis of the provided source code and property definitions.