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 a "Progress Shipping Event" (Evento De Progresso De Envio) within an integration system. It allows users to send detailed event data related to shipping progress, including customer information, order details, product metadata, and delivery parameters. This node is useful for tracking and updating the status of shipments in e-commerce or logistics workflows, enabling automated notifications or analytics based on shipping events.
Practical examples include:
- Automatically logging shipment progress when an order is dispatched.
- Sending updates to customers about their order status.
- Integrating with external systems to synchronize shipping events.
Properties
| Name | Meaning |
|---|---|
| ID | The identifier 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 | Collection of products involved in the order, each with: |
| - Nome Do Produto: Product name. | |
| - Quantidade Do Produto: Quantity of the product. | |
| - Valor Do Produto: Value of the product. | |
| Campo Produtos Obrigatório | Notice indicating that the products field is mandatory. |
| ID Do Pedido | Order ID associated with the event. |
| Valor Somado Dos Produtos Do Pedido | Sum total value of all products in the order. |
| Valor Do Pedido Total | Total order value including discounts and other charges. |
| 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, and street. |
| Parâmetros Adicionais (Delivery) | Delivery-related parameters such as tracking code, estimated delivery date, description, message, tracking URL, and freight value. |
Output
The node outputs JSON data representing the created shipping progress event. This output includes all the input properties structured into an event object suitable for further processing or integration with other systems. There is no indication of binary data output.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to connect to the external integration service.
- Depends on the external system that manages shipping events to accept and process the event data sent by this node.
Troubleshooting
- Missing Required Fields: Ensure all required fields like "ID", "Primeiro Nome", "Telefone", "Produtos", "ID Do Pedido", "Valor Somado Dos Produtos Do Pedido", "Valor Do Pedido Total", and "Desconto" are provided; otherwise, the node may fail to create the event.
- Invalid Date Formats: Dates such as "Data De Nascimento" and "Data De Estimativa De Entrega Do Pedido" must follow the specified format (YYYY-MM-DD). Incorrect formats can cause errors.
- 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 integration service will prevent event creation.
- Product Data Validation: Each product entry must have valid name, quantity, and value; missing or invalid data might cause rejection.
Links and References
- No direct links available from the source code.
- For best practices on event tracking and shipping updates, consult your external integration service documentation or API reference.