Actions48
- Custom Variable Actions
- Custom Variable Group Actions
- Event Actions
- Integration Actions
- Lead Actions
- Lead List Actions
Overview
The "Event - Order Paid" operation in this node is designed to send detailed information about a paid order event to an external service. This includes customer details, order specifics, product data, delivery information, and address parameters. It is useful for integrating e-commerce platforms or order management systems with notification or analytics services that track order payments.
Typical use cases include:
- Triggering notifications or workflows when an order payment is confirmed.
- Enriching customer profiles with purchase data.
- Feeding order payment events into marketing automation or CRM tools.
- Tracking sales and revenue metrics in real-time.
For example, after a customer completes payment on an online store, this node can send the order and customer data to a marketing platform to trigger a thank-you email or update customer segmentation.
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: YYYY-MM-DD) |
| 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 identifier |
| 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 the products field must be filled |
| 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, street |
| Delivery Parameters | Delivery details such as description, fee amount, message, tracking code, tracking URL, estimated delivery date |
Output
The node outputs JSON data representing the response from the external API after sending the "Order Paid" event. This typically includes confirmation of the event reception or any error messages returned by the API.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating requests to the external notification service.
- The node makes HTTP requests to the external API endpoint at
https://api.notificacoesinteligentes.com. - Proper configuration of authentication credentials within n8n is necessary.
Troubleshooting
- Missing required fields: Ensure all required properties like
ID,First Name,Phone,Products,Order ID,Order Products Total Value,Order Total Value, andDiscountare provided; otherwise, the API may reject the request. - Invalid date formats: The birthdate and estimated delivery date should follow the specified format (
YYYY-MM-DD) to avoid errors. - API timeouts or connectivity issues: Network problems or incorrect API credentials can cause request failures. Verify network access and credential validity.
- Incorrect product data structure: The products must be sent as an array of objects with correct keys (
name,quantity,value). Malformed data may lead to rejection. - Error messages from API: If the API returns errors, check the message for missing or invalid fields and adjust input accordingly.
Links and References
- Notificações Inteligentes API Documentation (assumed base URL)
- n8n documentation on HTTP Request Node for understanding how HTTP calls are made
- General best practices for e-commerce event tracking