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 delivery parameters. This node is useful for workflows that need to track or trigger actions when an order reaches the "processing" stage, such as updating CRM systems, notifying customers, or integrating with other order management tools.
Practical examples:
- Automatically logging order processing events into a marketing platform.
- Triggering notifications to warehouse or logistics teams when an order starts processing.
- Enriching customer profiles with order status updates in a database.
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 (required). 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 status description of the order |
| IP | Customer's IP address |
| Parâmetros Adicionais (Address) | Customer's 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 cost |
Output
The node outputs JSON data representing the created event with all the provided customer, order, product, and delivery information structured accordingly. The output can be used downstream in workflows for further processing or integration.
No binary data output is indicated.
Dependencies
- Requires an API key credential or similar authentication token to connect to the external service handling event creation.
- The node depends on proper configuration of this credential within n8n to authenticate requests.
- No additional external libraries are explicitly required beyond standard n8n environment.
Troubleshooting
- Missing Required Fields: Errors may occur if mandatory fields like "Primeiro Nome", "Telefone", "Produtos", "ID Do Pedido", or pricing fields are missing. Ensure all required 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.
- API Authentication Failures: If the API key or authentication token is invalid or missing, the node will fail to create the event. Verify credentials in n8n settings.
- Product Data Issues: Each product entry must include name, quantity, and value. Omitting any of these may result in incomplete event data or errors.
- Network or Service Errors: Connectivity issues or service downtime can prevent event creation. Check network access and service status.
Links and References
- No direct links available from the source code.
- For best practices on event-driven order processing, consider consulting documentation of your order management or CRM system.
- Refer to n8n documentation on creating custom nodes and managing credentials for setup guidance.