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 Pacote Saiu Para Entrega" (Create Event When Package Has Left for Delivery). This event typically captures detailed information about a customer's order and delivery status, including customer details, products involved, order totals, discounts, and delivery tracking information.
This node would be beneficial in e-commerce or logistics automation workflows where tracking the shipment status and notifying systems or users when a package has been dispatched is critical. For example, it can be used to trigger notifications to customers, update CRM records, or integrate with third-party shipping services once a package leaves the warehouse.
Properties
| Name | Meaning |
|---|---|
| Primeiro Nome | Customer's first name |
| Sobrenome | Customer's last name |
| Telefone | Customer's phone number including area code and country code |
| Customer's email address | |
| CPF/CNPJ | Customer's document number (CPF or CNPJ) |
| Data De Nascimento | Customer's birthdate in format YYYY-MM-DD |
| Gênero | Customer's gender |
| Moeda | Currency type used by the customer (e.g., BRL, USD, GBP) |
| Produtos | List of products in the order, each with: - Nome Do Produto (Product name) - Quantidade Do Produto (Quantity) - Valor Do Produto (Value) |
| ID Do Pedido | Order ID |
| 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 status description of the order for enrichment |
| Parâmetros Adicionais (Endereço) | Customer address details including: - Cidade (City) - Complemento (Complement) - País (Country) - Bairro (Neighborhood) - Número (House number) - CEP (Postal code) - Estado (State) - Rua (Street) |
| Parâmetros Adicionais (Entrega) | Delivery parameters including: - Código De Rastreio Da Entrega (Tracking code) - Data De Estimativa De Entrega Do Pedido (Estimated delivery date, UTC+0) - Descrição Da Entrega (Delivery description such as method or deadline) - Mensagem Da Entrega (Delivery message) - URL De Rastreio Da Entrega (Tracking URL) - Valor Do Frete Da Entrega (Shipping cost) |
Output
The node outputs JSON data representing the created event with all the provided input details structured accordingly. The output includes customer information, product details, order financials, and delivery tracking data. There is no indication that the node outputs binary data.
Dependencies
- The node likely requires an API key or authentication token to connect to the external service managing these events.
- Proper configuration of credentials within n8n is necessary to authenticate requests.
- No other explicit external dependencies are visible from the provided source code snippet.
Troubleshooting
- Missing Required Fields: Since many fields like "Primeiro Nome", "Telefone", "Produtos", "ID Do Pedido", and financial totals are required, omitting them will likely cause errors. Ensure all mandatory fields are filled.
- Invalid Date Formats: The birthdate and estimated delivery date require specific formats (YYYY-MM-DD). Incorrect formatting may lead to validation errors.
- Incorrect Phone Number Format: The phone number must include DDD and country code; otherwise, the event creation might fail.
- API Authentication Errors: If credentials are not set up correctly, the node will fail to authenticate with the external service.
- Product Data Issues: Each product entry must have a name, quantity, and value. Missing any of these could cause errors.
- Delivery Tracking URLs or Codes: Invalid or malformed tracking URLs or codes might not be accepted by the external system.
Links and References
- No direct links were provided in the source code or properties. Users should refer to their external event management or shipping service API documentation for more details on event creation and expected data formats.