Notificações Inteligentes

Overview

The node is designed to create an event specifically for a "Paid Order" scenario within an integration system. It collects detailed customer and order information, including personal data, products purchased, payment details, and delivery parameters. This node is useful in workflows where you want to trigger actions or notifications after an order has been successfully paid, such as updating CRM systems, sending confirmation emails, or logging sales events.

Practical examples:

• After a customer completes payment on an e-commerce platform, this node can send the order and customer details to a marketing automation tool.
• Triggering inventory updates or fulfillment processes once payment is confirmed.
• Logging paid order events into analytics platforms for sales tracking.

Properties

Name	Meaning
ID	The ID of the existing integration to which this event belongs.
Primeiro Nome (first_name)	Customer's first name (required).
Sobrenome (last_name)	Customer's last name.
Telefone (phone)	Customer's phone number including country code and area code (required).
Data De Nascimento (birthdate)	Customer's birth date in format YYYY-MM-DD.
Moeda (currency)	Currency type used by the customer (e.g., BRL, USD, GBP).
Gênero (gender)	Customer's gender.
Email	Customer's email address.
CPF/CNPJ	Customer's document number (CPF or CNPJ).
IP	Customer's IP address.
Produtos (products)	List of products in the order. Each product includes:
	- Nome Do Produto (productname): Product name (required).
	- Quantidade Do Produto (productquantity): Quantity of the product (required).
	- Valor Do Produto (productvalue): Value of the product (required).
Campo Produtos Obrigatório	Notice indicating that the products field is mandatory.
ID Do Pedido (orderid)	Order ID (required).
Valor Somado Dos Produtos Do Pedido (products_total)	Sum of all product values in the order (required).
Valor Do Pedido Total (total)	Total value of the order (required).
Desconto (discount)	Total discount applied to the order (required).
Status	Current status description of the order for enrichment purposes.
Parâmetros Adicionais (addressparameter)	Additional customer address details including city, complement, country, neighborhood, number, postal code, state, and street.
Parâmetros Adicionais (deliveryparameter)	Delivery-related details including tracking code, estimated delivery date, description, message, tracking URL, and freight value.

Output

The node outputs JSON data representing the created "Paid Order" event with all the provided customer, order, product, and delivery details structured accordingly. This output can be used downstream in the workflow for further processing, logging, or integration with other systems.

If binary data were involved (not indicated here), it would typically represent files or attachments related to the event, but this node focuses on structured JSON data only.

Dependencies

• Requires an API key credential or similar authentication token configured in n8n to connect to the external integration service.
• The node depends on the external integration platform that accepts event creation requests.
• Proper configuration of the integration ID and access permissions is necessary.

Troubleshooting

• Missing required fields: Errors may occur if mandatory fields like first_name, phone, products, orderid, products_total, total, or discount are not provided. Ensure these are filled correctly.
• Invalid data formats: For example, the birthdate should follow the YYYY-MM-DD format; incorrect formatting might cause errors.
• API authentication failures: If the API key or credentials are missing or invalid, the node will fail to create the event.
• Network issues: Connectivity problems with the external integration service can cause timeouts or request failures.
• Data validation errors: Providing inconsistent totals (e.g., products_total not matching sum of product values) might lead to rejection by the API.

To resolve these issues:

• Double-check all required inputs.
• Validate data formats before execution.
• Confirm API credentials and network connectivity.
• Review error messages returned by the external service for specific guidance.

Links and References

• No direct links available from the source code.
• Refer to your integration platform’s API documentation for event creation specifics.
• Use standard date format references for input validation (ISO 8601).