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 operation "Criar Evento De Pedido Estornado" (Create Refunded Order Event) is designed to create an event representing a refunded order within an integration or event system. This node is useful for workflows that need to track, log, or react to refund events in e-commerce or order management systems. For example, it can be used to notify other systems about refunds, update customer records, or trigger follow-up actions such as sending refund confirmation emails.
Properties
| Name | Meaning |
|---|---|
| ID | The ID of the existing integration. |
| Primeiro Nome | Customer's first name. |
| Sobrenome | Customer's last name. |
| Telefone | Customer's phone number including country code and area code (DDD). |
| 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 | List of products involved in the order, each with: |
| - Nome Do Produto (Product name) | |
| - Quantidade Do Produto (Product quantity) | |
| - Valor Do Produto (Product value) | |
| Campo Produtos Obrigatório | Notice indicating that product data is required. |
| ID Do Pedido | The order ID. |
| 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 customer address parameters including city, complement, country, neighborhood, number, postal code, state, 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 output typically includes all the input properties structured into an event object suitable for downstream processing or integration with other systems. There is no indication of binary data output.
Dependencies
- Requires connection to an external integration or event management API where the refunded order event will be created.
- Needs an API key or authentication token configured in n8n credentials to authorize requests.
- No additional external libraries are indicated beyond standard n8n environment.
Troubleshooting
- Missing Required Fields: Ensure all required fields such as "ID", "Primeiro Nome", "Telefone", "Produtos", "ID Do Pedido", "Valor Somado Dos Produtos Do Pedido", "Valor Do Pedido Total", and "Desconto" are provided; missing these may cause errors.
- Invalid Date Format: The birthdate and delivery estimate date must follow the specified format (YYYY-MM-DD); incorrect formats may lead to rejection by the API.
- API Authentication Errors: Verify that the API key or authentication token is correctly set up in n8n credentials.
- Network Issues: Connectivity problems with the external service can cause timeouts or failures.
- Data Validation: Check that numeric fields like quantities, values, totals, and discounts are valid numbers.
Links and References
- No direct links available from the source code.
- Users should refer to their specific integration or event platform API documentation for detailed requirements on event creation and field formats.