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 operation "Criar Evento De Aguardando Pagamento" (Create Event Waiting for Payment) is designed to create an event that signals a pending payment status for an order. This is useful in e-commerce or payment processing workflows where you want to track orders that are awaiting payment confirmation, such as bank deposits, PIX payments, or credit card transactions.
Typical use cases include:
- Triggering follow-up actions or notifications when an order is created but not yet paid.
- Integrating with payment gateways to monitor payment status.
- Automating reminders or updates based on the payment method and status.
For example, when a customer places an order and chooses PIX as the payment method, this node can create an event containing all relevant payment details (like QR code, due date, and amount), which downstream nodes can use to send reminders or update order status.
Properties
| Name | Meaning |
|---|---|
| Primeiro Nome | Customer's first name |
| Sobrenome | Customer's last name |
| Telefone | Customer's phone number including country and area codes |
| Data De Nascimento | Customer's birthdate in format YYYY-MM-DD |
| Moeda | Currency type used by the customer (e.g., BRL, USD, GBP) |
| Gênero | Customer's gender |
| CPF/CNPJ | Customer's document number (CPF or CNPJ) |
| IP | Customer's IP address |
| Produtos | List of products in the order, each with: product name, quantity, and value |
| Campo Produtos Obrigatório | Notice indicating that the products field is mandatory |
| 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 enrichment |
| Método De Pagamento | Payment method; options: Cartão De Crédito (credit-card), Depósito (deposit), PIX (pix) |
| Código Bacen | Bacen code for PIX payment (required if payment method is PIX) |
| Data Do Vencimento Do Pix | Due date/time for PIX payment in UTC+0 timezone (required if payment method is PIX) |
| QR Code | QR code string for PIX payment (required if payment method is PIX) |
| URL De Pagamento Do Pix | URL for PIX payment (required if payment method is PIX) |
| Valor Do Pix | Amount for PIX payment (required if payment method is PIX) |
Output
The node outputs JSON data representing the created event with all the provided input details structured accordingly. The output includes customer information, order details, payment method specifics, and product metadata.
If the payment method is PIX, the output will also contain PIX-specific fields such as QR code, payment URL, due date, and Bacen code.
No binary data output is indicated.
Dependencies
- The node likely requires access to an external API or service to register or dispatch the event, though the bundled source code does not explicitly show this.
- An API key or authentication token is probably needed to interact with the external system managing these events.
- Proper configuration of credentials and environment variables within n8n is necessary to enable communication with the external service.
Troubleshooting
- Missing Required Fields: Ensure all required fields like "Primeiro Nome," "Telefone," "Produtos," "ID Do Pedido," and payment-specific fields (e.g., Bacen code for PIX) are provided.
- Invalid Date Formats: The "Data De Nascimento" and "Data Do Vencimento Do Pix" must be in correct formats (YYYY-MM-DD for birthdate, ISO 8601 for datetime).
- Payment Method Mismatch: If the payment method is PIX, all PIX-related fields must be filled; otherwise, errors may occur.
- API Authentication Errors: Verify that the API key or authentication credentials are correctly set up in n8n.
- Network Issues: Check connectivity to the external service endpoint.
Links and References
- PIX Payment System
- Brazilian Central Bank (Bacen)
- General n8n documentation on creating custom nodes and handling events: https://docs.n8n.io/