Actions45
- Evento Actions
- Criar Evento De Acesso Concedido
- Criar Evento De Aguardando Pagamento
- Criar Evento De Boleto Impresso
- Criar Evento De Carrinho Abandonado
- Criar Evento De Nota Nps
- Criar Evento De Pacote Aguardando Retirada
- Criar Evento De Pacote Saiu Para Entrega
- Criar Evento De Pedido Cancelado
- Criar Evento De Pedido Despachado
- Criar Evento De Pedido Entregue
- Criar Evento De Pedido Estornado
- Criar Evento De Pedido Pago
- Criar Evento De Pedido Processando
- Criar Evento De Pesquisa Nps
- Criar Evento De Progresso De Envio
- Criar Evento De Redefinicao De Senha
- Gerenciamento Da Conta Actions
- Grupo De Variável Customizada Actions
- Integração Actions
- Lead Actions
- Lista De Lead Actions
- Variável Customizada Actions
Overview
The node is designed to create an event specifically for a refunded order ("Criar Evento De Pedido Estornado"). It collects detailed information about the customer, the order, and the products involved in the refunded order event. This node would be beneficial in scenarios where businesses want to track refund events in their workflow automation, such as updating CRM systems, triggering notifications, or syncing refund data with other platforms.
Practical examples include:
- Automatically logging refund events into a customer database.
- Triggering email notifications to customers or support teams when an order is refunded.
- Updating inventory or financial records based on refunded orders.
Properties
| Name | Meaning |
|---|---|
| ID | The ID of the existing integration. |
| Primeiro Nome | Customer's first name. |
| Telefone | Customer's phone number including country code and area code (DDD). |
| Sobrenome | Customer's last name. |
| Data De Nascimento | Customer's birthdate in format YYYY-MM-DD (e.g., 2001-08-20). |
| Moeda | Currency type used by the customer (e.g., BRL, USD, GBP). |
| Gênero | Customer's gender. |
| Customer's email address. | |
| CPF/CNPJ | Customer's document number (CPF or CNPJ). |
| IP | Customer's IP address. |
| Produtos | Collection of product details related to the order. Each product includes: |
| - Nome Do Produto (Product name) | |
| - Quantidade Do Produto (Product quantity) | |
| - Valor Do Produto (Product value) | |
| Campo Produtos Obrigatório | Notice indicating that the products field is mandatory. |
| ID Do Pedido | Order ID associated with the refunded order event. |
| Valor Somado Dos Produtos Do Pedido | Sum of the values of all products in the order. |
| Valor Do Pedido Total | Total value of the order. |
| Desconto | Total discount applied to the order. |
| Status | Current status description of the order for enrichment purposes. |
| Parâmetros Adicionais (Address) | Additional address parameters of the customer including city, complement, country, neighborhood, number, postal code, state, and street. |
| Parâmetros Adicionais (Delivery) | Additional delivery parameters including tracking code, estimated delivery date, description, message, tracking URL, and freight value. |
Output
The node outputs JSON data representing the created refunded order event. This JSON will contain all the input properties structured accordingly, reflecting the customer's details, order information, product list, and any additional address or delivery parameters provided.
There is no indication that the node outputs binary data.
Dependencies
- The node requires an API key or authentication token to connect to the external service handling event creation (not explicitly shown but implied by the need for an integration ID).
- Proper configuration of this credential within n8n is necessary.
- No other external dependencies are indicated in the provided source code snippet.
Troubleshooting
- Missing Required Fields: Errors may occur if required fields like "ID", "Primeiro Nome", "Telefone", "Produtos", "ID Do Pedido", "Valor Somado Dos Produtos Do Pedido", "Valor Do Pedido Total", or "Desconto" are not provided. Ensure all mandatory inputs are filled.
- Invalid Date Format: The "Data De Nascimento" and delivery "orderdate" fields require specific date formats (YYYY-MM-DD). Incorrect formatting may cause errors.
- Incorrect Currency Codes: Using unsupported or invalid currency codes in the "Moeda" field might lead to failures.
- API Authentication Issues: If the integration ID or API credentials are incorrect or missing, the node will fail to create the event.
- Product Details: The "Produtos" collection must have at least one product with valid name, quantity, and value; otherwise, the event creation may fail.
Links and References
- No direct links or references were found in the provided source code or property definitions.
- For best practices on event tracking and refund management, consult your external service's API documentation or n8n community forums.