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 pickup.
Practical examples include:
- Notifying a customer that their online order is ready for pickup at a store.
- Updating internal systems when a package arrives at a pickup location.
- Triggering subsequent automation steps such as sending SMS or email notifications 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 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 enriching information |
| Parâmetros Adicionais (Endereço) | Additional address parameters including city, complement, country, neighborhood, number, postal code, state, street |
| Parâmetros Adicionais (Entrega) | Additional delivery parameters 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 details about the customer, order, products, and delivery information. The output structure reflects the input properties enriched with any processing results or confirmations from the event creation process.
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 event data only.
Dependencies
- Requires an API key credential or similar authentication token to connect to the external service managing 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 operation.
Troubleshooting
- Missing Required Fields: Errors may occur if mandatory fields like "Primeiro Nome", "Telefone", "Produtos", or "ID Do Pedido" are not provided. Ensure all required inputs are filled.
- Invalid Date Format: The "Data De Nascimento" and "Data De Estimativa De Entrega Do Pedido" must follow the YYYY-MM-DD format. Incorrect formats can 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 configured and has sufficient permissions.
- Network Issues: Connectivity problems between n8n and the external event service can cause timeouts or failures. Check network settings and service availability.
- Incorrect Currency Codes: Use standard currency codes (e.g., BRL, USD, GBP) to avoid errors related to unsupported currencies.
Links and References
- No direct links available from the source code. For more information, consult the documentation of the external event management system integrated with this node.