Actions48
- Custom Variable Actions
- Custom Variable Group Actions
- Event Actions
- Integration Actions
- Lead Actions
- Lead List Actions
Overview
The "Event - Order Dispatched" operation is designed to send detailed event data when an order has been dispatched. This node is useful in scenarios where businesses want to track and notify systems or services about the dispatch status of customer orders. It helps integrate order dispatch events into workflows, enabling automated notifications, analytics, or further processing based on order shipment.
Practical examples include:
- Sending order dispatch information to a CRM or marketing platform to trigger follow-up communications.
- Updating inventory or logistics systems with shipping details.
- Logging dispatch events for audit or reporting purposes.
Properties
| Name | Meaning |
|---|---|
| ID | The ID of the existing integration |
| First Name | Customer’s first name |
| Last Name | Customer’s last name |
| Phone | Customer phone number including country and area code |
| Birth Date | Customer’s birth date (format: Year-Month-Day, e.g., 2001-08-20) |
| Currency | Currency used by the customer (e.g., BRL, USD, GBP) |
| Gender | Customer’s gender |
| Customer’s email address | |
| Tax ID (CPF/CNPJ) | Customer’s tax document identification |
| IP Address | Customer’s IP address |
| Products | List of products in the order, each with: Product Name, Quantity, and Value |
| Products Field Is Required | Notice indicating that product data must be provided |
| Order ID | Unique identifier for 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 for enrichment |
| Address Parameters | Customer address details including city, complement, country, neighborhood, number, postal code, state, and street |
| Delivery Parameters | Delivery details including description, fee amount, message, tracking code, tracking URL, and estimated delivery date |
Output
The node outputs JSON data representing the dispatched order event. This includes all the input properties structured under customer, order, address, and delivery fields as applicable. The output can be used downstream in workflows to trigger other actions or integrations.
No binary data output is indicated.
Dependencies
- Requires access to an external API endpoint at
https://api.notificacoesinteligentes.comfor some operations (e.g., loading tags), but this may not be directly related to the "Order Dispatched" operation. - Requires proper authentication credentials (an API key or token) configured in n8n to authorize requests.
- The node uses HTTP requests internally to communicate with the external service.
Troubleshooting
- Missing required fields: Ensure all required fields such as ID, First Name, Phone, Products, Order ID, Products Total, Total, and Discount are provided; missing these will likely cause errors.
- Invalid date formats: The birthdate and estimated delivery date should follow the specified format (ISO date strings). Incorrect formatting may cause request failures.
- API authentication errors: If the API key or token is invalid or missing, requests will fail. Verify credentials in n8n settings.
- Network timeouts or connectivity issues: The node sets a timeout of 5 seconds for HTTP requests; slow or unreachable endpoints may cause errors.
- Incorrect property mappings: Ensure that the input data matches the expected structure, especially for nested objects like products, address, and delivery parameters.
Links and References
- Notificações Inteligentes API Documentation (assumed from baseURL)
- n8n Documentation on Creating Custom Nodes
- General best practices for Handling Dates in APIs
This summary is based solely on static analysis of the provided source code and property definitions.