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 the scenario "Criar Evento De Pedido Despachado" (Create Order Dispatched Event). This event typically represents the moment when an order has been dispatched or shipped to the customer. It is useful in workflows that track order fulfillment status, notify customers about shipment, update inventory systems, or trigger downstream logistics processes.
Practical examples include:
- Sending a notification email or SMS to the customer informing them their order has been dispatched.
- Updating a CRM or ERP system with the shipping status.
- Triggering further automation such as generating invoices or updating delivery tracking information.
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 |
| Data De Nascimento | Customer's birthdate in format YYYY-MM-DD |
| 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 - Brazilian tax IDs) |
| IP | Customer's IP address |
| Produtos | Collection of products 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 mandatory |
| ID Do Pedido | Order ID |
| Valor Somado Dos Produtos Do Pedido | Sum of all product values in the order |
| Valor Do Pedido Total | Total order value |
| Desconto | Total discount applied to the order |
| Status | Current status description of the order for enrichment |
| Parâmetros Adicionais (Address) | Customer address details including city, complement, country, neighborhood, number, postal code, state, street |
| Parâmetros Adicionais (Delivery) | Delivery details including tracking code, estimated delivery date, description, message, tracking URL, freight cost |
Output
The node outputs JSON data representing the created event with all the provided input properties structured accordingly. This output can be used in subsequent workflow steps for logging, notifications, or further processing.
There is no indication of binary data output for this operation.
Dependencies
- The node likely requires an API key or authentication token to connect to the external service managing these events.
- Proper configuration of the integration ID is necessary to link the event to the correct system.
- No explicit external libraries are indicated beyond the bundled source code.
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 Formats: The birthdate and delivery estimate date must follow the specified formats (e.g., YYYY-MM-DD). Incorrect formatting may cause errors.
- Incorrect Currency Codes: Use standard currency codes (ISO 4217) to avoid validation issues.
- API Authentication Failures: If the node cannot authenticate with the external service, verify that the API key or credentials are correctly configured in n8n.
- Network Issues: Connectivity problems to the external API endpoint may cause timeouts or failures.
Links and References
- No direct links available from the source code.
- For best practices on event creation and order dispatch workflows, consult your external service's API documentation or general e-commerce order management resources.