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 related to an order being processed ("Criar Evento De Pedido Processando"). It collects detailed customer and order information, including personal data, products in the order, pricing details, and additional parameters such as delivery and address information. This node would be beneficial in e-commerce or order management workflows where tracking and logging the state of orders is necessary for analytics, notifications, or integration with other systems.
Practical examples include:
- Logging when an order status changes to "processing" to trigger downstream processes.
- Sending enriched order data to a CRM or marketing platform.
- Tracking customer behavior and order details for reporting or auditing.
Properties
| Name | Meaning |
|---|---|
| Primeiro Nome | Customer's first name (required) |
| Sobrenome | Customer's last name |
| Telefone | Customer's phone number including country code and area code (required) |
| 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 product includes: |
| - Nome Do Produto (product name, required) | |
| - Quantidade Do Produto (product quantity, required) | |
| - Valor Do Produto (product value, required) | |
| ID Do Pedido | Order ID (required) |
| Valor Somado Dos Produtos Do Pedido | Sum of all product values in the order (required) |
| Valor Do Pedido Total | Total order value including discounts (required) |
| Desconto | Total discount applied to the order (required) |
| Status | Current description of the order status |
| 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 customer, order, product, and additional parameters structured accordingly. The output can be used for further processing or integration within n8n workflows.
If binary data were involved, it would typically represent files or attachments related to the event, but this node focuses on structured JSON data only.
Dependencies
- Requires an API key credential or similar authentication token to connect to the external service handling events.
- The node depends on proper configuration of the integration ID and access credentials.
- No explicit external libraries are indicated beyond standard n8n dependencies.
Troubleshooting
- Missing Required Fields: Errors may occur if required fields like "Primeiro Nome", "Telefone", "Produtos", "ID Do Pedido", or pricing fields are missing. Ensure all mandatory inputs are provided.
- Invalid Date Formats: The birthdate and delivery estimate date must follow the specified formats (e.g., YYYY-MM-DD). Incorrect formatting may cause errors.
- Incorrect Currency Codes: Use valid ISO currency codes to avoid issues with currency handling.
- API Authentication Failures: Verify that the API key or authentication token is correctly configured and has sufficient permissions.
- Product Data Issues: Each product entry must have a name, quantity, and value. Missing any of these will likely cause validation errors.
Links and References
- ISO 4217 Currency Codes
- Date Format Reference (ISO 8601)
- General n8n documentation on creating custom nodes: https://docs.n8n.io/integrations/creating-nodes/