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 "Pedido Entregue" (Order Delivered) within an integration system. It collects detailed customer and order information, including personal data, order details, product metadata, delivery parameters, and more. This node is useful in workflows where you want to notify or log that a customer's order has been delivered, enabling downstream processes such as updating CRM systems, triggering notifications, or analytics.
Practical examples:
- After confirming an order delivery in an e-commerce platform, use this node to send the delivery event to a marketing automation tool.
- Log delivery events into a customer database to track delivery performance and customer satisfaction.
- Trigger follow-up surveys or feedback requests once an order is marked as delivered.
Properties
| Name | Meaning |
|---|---|
| ID | The ID of the existing integration to which this event belongs. |
| 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, Brazilian tax identifiers). |
| 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) | |
| 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 purposes. |
| 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 (UTC+0), description, message, tracking URL, and freight value. |
Output
The node outputs JSON data representing the created event with all the provided customer, order, product, and delivery details structured accordingly. This output can be used in subsequent workflow steps for logging, notification, or further processing.
If binary data were involved (not indicated here), it would typically represent files or attachments related to the event, but this node focuses on structured JSON event data only.
Dependencies
- Requires an active integration identified by the provided integration ID.
- Likely depends on an API key or authentication token configured in n8n credentials to communicate with the external service handling these events.
- No other explicit external dependencies are indicated from the source code snippet.
Troubleshooting
- Missing Required Fields: The node requires certain fields like integration ID, first name, phone, products, order ID, totals, and discount. Omitting these will likely cause errors.
- Invalid Date Formats: Birthdate and delivery estimate dates must follow the specified formats (YYYY-MM-DD). Incorrect formatting may lead to rejection by the API.
- Incorrect Currency Codes: Using unsupported or invalid currency codes might cause failures.
- API Authentication Errors: Ensure the API key or authentication token is correctly set up in n8n credentials.
- Network Issues: Connectivity problems with the external service could cause timeouts or failed requests.
Common error messages might include missing required parameters, invalid data format, or authentication failures. To resolve, verify all required inputs, confirm correct formatting, and check credential configurations.
Links and References
- No direct links available from the provided source code.
- For best results, consult the documentation of the external integration service handling these events.
- General references for Brazilian document formats (CPF/CNPJ) and currency codes may help ensure correct input data.