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 event-driven 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 track or trigger actions based on the delivery of an order, such as updating CRM systems, notifying customers, or logging delivery events for analytics.
Practical examples:
- Automatically sending a thank-you email or SMS when an order is marked as delivered.
- Updating inventory or sales records after delivery confirmation.
- Triggering follow-up surveys or feedback requests post-delivery.
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, 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) | |
| Campo Produtos Obrigatório | Notice indicating that the products field 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 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 including city, complement, country, neighborhood, number, postal code, state, street. |
| Parâmetros Adicionais (Delivery) | Delivery-related parameters including tracking code, estimated delivery date, 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 downstream in the workflow for further processing, logging, or triggering other actions.
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 data only.
Dependencies
- Requires an API key credential or similar authentication token to connect to the external event integration service.
- Needs proper configuration of the integration ID to identify the target integration.
- The node depends on the external event management system accepting these event payloads.
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 missing or empty. Ensure all mandatory inputs are provided.
- Invalid Date Formats: The birthdate and delivery estimate date must follow the specified formats (YYYY-MM-DD). Incorrect formatting may cause errors.
- Incorrect Currency Codes: Use standard currency codes (e.g., BRL, USD) to avoid validation issues.
- API Authentication Failures: Verify that the API key or authentication token is correctly configured and has sufficient permissions.
- Network Issues: Connectivity problems with the external service will prevent event creation; check network settings and service availability.
Links and References
- ISO 4217 Currency Codes
- Brazilian CPF and CNPJ Documentation
- General best practices for event-driven integrations and webhook usage (varies by platform).