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 of type "Criar Evento De Pacote Aguardando Retirada" (Create Package Awaiting Pickup Event). This event typically represents a status update in an order or delivery process where a package is ready and waiting to be picked up by the customer or a courier. It is useful in e-commerce, logistics, or delivery management workflows to notify systems or users about the readiness of a package for collection.
Practical examples include:
- Notifying a customer that their online order has arrived at a pickup location.
- Updating internal systems when a package reaches a warehouse or store for customer pickup.
- Triggering subsequent automation steps such as sending SMS or email alerts to customers.
Properties
| Name | Meaning |
|---|---|
| Primeiro Nome | Customer's first name |
| Sobrenome | Customer's last name |
| Telefone | Customer's phone number including country code and area 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) |
| IP | Customer's IP address |
| Produtos | List of products included in the order; each product includes: |
| - 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 information enrichment |
| 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, description, message, tracking URL, freight value |
Output
The node outputs JSON data representing the created event with all the provided input properties structured accordingly. The output JSON will contain detailed information about the customer, order, products, and delivery parameters reflecting the event "Package Awaiting Pickup."
If binary data were involved (not indicated here), it would represent attachments or files related to the event, but this node focuses on structured JSON event data only.
Dependencies
- Requires an API key credential or similar authentication token to connect to the external service handling events.
- The node depends on an external event management or integration platform where these events are registered.
- Proper configuration of credentials and endpoint URLs within n8n is necessary for successful execution.
Troubleshooting
- Missing Required Fields: Ensure all required fields like "Primeiro Nome," "Telefone," "Produtos," and "ID Do Pedido" are provided; missing these will cause errors.
- 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 Currency Codes: Use valid ISO currency codes (e.g., BRL, USD) to avoid validation errors.
- API Authentication Errors: Verify that the API key or authentication token is correctly configured and has sufficient permissions.
- Network Issues: Check connectivity to the external event service if requests time out or fail.
Links and References
- No direct links available from the source code.
- For best practices, refer to documentation of the external event management system integrated with this node.
- General guidance on event-driven automation can be found in n8n community forums and official docs.