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 canceled order within an integration system. It collects detailed customer and order information to register the cancellation event, which can be useful for tracking order statuses, triggering workflows upon cancellations, or updating external systems about the cancellation.
Practical examples include:
- Automatically notifying a CRM or ERP system when a customer's order is canceled.
- Triggering follow-up actions such as sending a cancellation confirmation email or restocking inventory.
- Logging cancellation events for analytics or auditing purposes.
Properties
| Name | Meaning |
|---|---|
| ID | The identifier of the existing integration where the event will be created. |
| Primeiro Nome | Customer's first name. |
| Sobrenome | Customer's last name (optional). |
| Data De Nascimento | Customer's birthdate in format YYYY-MM-DD (optional). |
| Moeda | Currency type used by the customer (e.g., BRL, USD, GBP). |
| Gênero | Customer's gender (optional). |
| Customer's email address (optional). | |
| Telefone | Customer's phone number including country code and area code. |
| CPF/CNPJ | Customer's document number (CPF or CNPJ) (optional). |
| IP | Customer's IP address (optional). |
| Produtos | List of products involved in the order. Each product includes: |
| - Nome Do Produto: Product name. | |
| - Quantidade Do Produto: Quantity of the product. | |
| - Valor Do Produto: Value of the product. | |
| ID Do Pedido | Order ID associated with the canceled order. |
| Valor Somado Dos Produtos Do Pedido | Sum of all product values 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 additional context (optional). |
| Parâmetros Adicionais (Endereço) | Customer's address details including city, complement, country, neighborhood, number, postal code, state, and street (optional). |
| Parâmetros Adicionais (Entrega) | Delivery details including tracking code, estimated delivery date, description, message, tracking URL, and freight cost (optional). |
Output
The node outputs JSON data representing the created canceled order event. This output typically contains the structured event data sent to the integration system, confirming the event creation and possibly including identifiers or status messages returned from the external service.
No binary data output is indicated.
Dependencies
- Requires connection to an external integration platform or API that manages events related to orders.
- Needs an API key or authentication token configured in n8n credentials to authorize event creation.
- Proper configuration of the integration ID is necessary to target the correct integration instance.
Troubleshooting
- Missing Required Fields: Errors may occur if mandatory 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 required inputs are filled.
- Invalid Data Formats: Date fields should follow the specified format (e.g., birthdate as YYYY-MM-DD). Incorrect formats might cause validation errors.
- API Authentication Failures: If the API key or authentication token is invalid or missing, the node will fail to create the event. Verify credential setup.
- Network Issues: Connectivity problems with the external integration service can cause timeouts or failures.
- Incorrect Integration ID: Using an invalid or non-existent integration ID will prevent event creation.
Links and References
- No direct links available from the source code.
- For best practices on event-driven integrations and order management, consult your integration platform’s official documentation.