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 a "Paid Order" scenario within an integration system. It collects detailed customer and order information when an order payment is confirmed, enabling workflows that react to this event. This can be useful for automating post-payment processes such as sending confirmation emails, updating CRM systems, triggering shipment workflows, or analytics tracking.
Practical examples:
- Automatically notify the warehouse to start packing after payment confirmation.
- Update customer loyalty points based on paid orders.
- Send personalized thank-you messages including order details.
- Integrate with accounting software to register paid invoices.
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 |
| IP | Customer's IP address |
| 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: Quantity of the product (required) | |
| - Valor Do Produto: Value/price of the product (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 value of the order including discounts (required) |
| Desconto | Total discount applied to the order (required) |
| Status | Current status description of the order |
| Parâmetros Adicionais (Endereço) | Additional address parameters of the customer, including: |
| - Cidade (City), Complemento (Complement), País (Country), Bairro (Neighborhood), Número (Number), CEP (Postal Code), Estado (State), Rua (Street) | |
| Parâmetros Adicionais (Entrega) | Additional 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) | |
| - 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 "Paid Order" event. This JSON contains all the input properties structured appropriately, reflecting the customer's personal data, order details, product list, and additional address and delivery parameters.
If binary data output is supported, it would typically represent attachments or documents related to the order event, but no explicit binary output is indicated here.
Dependencies
- Requires an API key or authentication token to connect to the external integration service where the event is created.
- The node depends on the external system's API endpoint to accept event creation requests.
- Proper configuration of credentials and endpoint URLs in n8n is necessary.
Troubleshooting
- Missing required fields: Errors may occur if mandatory fields like "Primeiro Nome", "Telefone", "Produtos", "ID Do Pedido", or monetary values are missing. Ensure all required inputs are provided.
- Invalid data formats: Date fields should follow the specified format (e.g., YYYY-MM-DD). Incorrect formatting may cause API rejection.
- API authentication errors: If the API key or token is invalid or expired, the node will fail to create the event. Verify credential validity.
- Network issues: Connectivity problems to the external API will prevent event creation. Check network access and proxy settings.
- Data validation errors: Some APIs enforce strict validation on fields like currency codes or product quantities; ensure these conform to expected standards.
Links and References
- No direct links available from the source code.
- For best results, consult the external integration platform's API documentation related to event creation and order payment events.