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" (Criar Evento De Progresso De Envio) within an event management or integration system. It collects detailed customer and order information, including personal data, product details, and delivery parameters, to register or update the progress of a shipping event related to an order.
This node is beneficial in scenarios where businesses want to track and log shipping progress events automatically as part of their workflow automation. For example, e-commerce platforms can use it to notify customers about shipment status updates, or logistics companies can integrate it to keep internal systems synchronized with shipping milestones.
Practical examples:
- Automatically creating a shipping progress event when an order is dispatched.
- Logging delivery tracking codes and estimated delivery dates for customer notifications.
- Updating order status with enriched customer and product metadata during shipping.
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 of the values of all products in the order. |
| Valor Do Pedido Total | Total value of the order. |
| Desconto | Total discount applied to the order. |
| Status | Current descriptive status 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 including tracking code, estimated delivery date, description, message, tracking URL, and freight value. |
Output
The node outputs JSON data representing the created or updated shipping progress event. This output includes all the input properties structured into a coherent event object, reflecting customer details, order specifics, product metadata, and delivery information.
If binary data were supported, it would typically represent attachments or documents related to the event, but this node focuses on structured JSON event data only.
Dependencies
- Requires access to an external API or service that manages event creation and shipping progress updates.
- Needs an API key or authentication token configured in n8n credentials to authorize requests.
- Proper configuration of environment variables or credentials for the target integration platform is necessary.
Troubleshooting
- Missing Required Fields: Errors may occur if required fields like "ID", "Primeiro Nome", "Telefone", "Produtos", or "ID Do Pedido" are not provided. Ensure all mandatory inputs are filled.
- Invalid Date Format: The "Data De Nascimento" and "orderdate" fields require specific date formats (YYYY-MM-DD). Incorrect formatting may cause validation errors.
- API Authentication Failures: If the node cannot authenticate with the external service, verify that the API key or authentication token is correctly set up in n8n.
- Network Issues: Connectivity problems with the external API will prevent event creation. Check network settings and endpoint availability.
- Data Type Mismatches: Numeric fields such as quantities, values, totals, and discounts must be numbers; providing strings or invalid types may cause errors.
Links and References
- No direct links available from the source code.
- Users should refer to the documentation of the external event management or shipping progress API integrated with this node.
- General n8n documentation on creating custom nodes and managing credentials: https://docs.n8n.io/