Notificações Inteligentes icon

Notificações Inteligentes

Integração do NI

Actions45

Overview

The node is designed to create an event specifically for a canceled order within an integration system. It collects detailed information about the canceled order, including customer details, order specifics, product data, and additional parameters related to delivery and address. This node is useful in scenarios where businesses want to track or react to order cancellations by sending structured event data to another system or workflow.

Practical examples include:

  • Notifying a CRM or marketing platform about a canceled order to update customer status.
  • Triggering internal workflows for inventory restocking or refund processing.
  • Logging cancellation events for analytics or auditing purposes.

Properties

Name Meaning
Primeiro Nome Customer's first name
Sobrenome Customer's last name
Telefone Customer's phone number including country code and area code
Email Customer's email address
CPF/CNPJ Customer's document number (CPF or CNPJ)
Data De Nascimento Customer's birthdate in format YYYY-MM-DD
Gênero Customer's gender
IP Customer's IP address
Produtos List of products in the order, each with: Product Name, Quantity, and Value
Campo Produtos Obrigatório Notice indicating that the products field is mandatory
ID Do Pedido Unique identifier of the order
Valor Somado Dos Produtos Do Pedido Sum total value of all products in the order
Valor Do Pedido Total Total value of the order including discounts and other charges
Desconto Total discount applied to the order
Status Current status description of the order
Parâmetros Adicionais (Endereço) Customer's address details including city, complement, country, neighborhood, number, postal code, state, and street
Parâmetros Adicionais (Entrega) Delivery details such as tracking code, estimated delivery date, description, message, tracking URL, and freight cost

Output

The node outputs JSON data representing the created canceled order event. The output includes all the input properties structured into a single event object, suitable for downstream processing or integration with other systems.

There is no indication that the node outputs binary data.

Dependencies

  • The node likely requires an API key or authentication token to connect to the external integration service where the event is created.
  • Proper configuration of this credential within n8n is necessary.
  • No other explicit external dependencies are indicated in the provided source code snippet.

Troubleshooting

  • Missing Required Fields: Errors may occur if required fields like "ID Do Pedido", "Produtos", or "Primeiro Nome" are missing. Ensure all mandatory inputs are provided.
  • Invalid Data Formats: Date fields should follow the specified format (e.g., YYYY-MM-DD). Incorrect formats might cause failures.
  • API Authentication Issues: If the node cannot authenticate with the external service, verify that the API key or token is correctly configured and valid.
  • Network or Service Errors: Connectivity problems or service downtime can cause errors; check network access and service status.

Links and References

  • No direct links were found in the source code or property definitions.
  • For best practices on event-driven integrations and order management, consider consulting documentation of the target integration platform or general API event handling guides.

Discussion