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 the operation "Criar Evento De Boleto Impresso" (Create Printed Boleto Event) within the "Evento" resource. This event typically involves registering or logging details related to a boleto payment slip that has been printed for a customer. Such a node would be beneficial in e-commerce, billing systems, or financial platforms where tracking boleto issuance and printing events is necessary for order management, customer notifications, or compliance.
Practical examples include:
- Automatically logging when a boleto payment slip is generated and printed for a customer.
- Triggering follow-up workflows such as sending reminders before boleto expiration.
- Integrating with CRM or ERP systems to update order/payment status based on boleto events.
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 (format: YYYY-MM-DD) |
| Gênero | Customer's gender |
| IP | Customer's IP address |
| Produtos | List of products involved 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 all product values in the order |
| Valor Do Pedido Total | Total order value |
| Desconto | Total discount applied to the order |
| Status | Current status description of the order for enrichment |
| Link Para O Boleto Em HTML | URL link to the boleto in HTML format |
| Link Para O Boleto Em PDF | URL link to view the boleto in PDF format (optional) |
| Linha Digitável Do Boleto | The barcode line of the boleto |
| Valor Do Boleto | Value of the boleto |
| Data Do Vencimento Do Boleto | Due date of the boleto in UTC+0 timezone (important for boleto reminder functionality) |
| Parâmetros Adicionais | Additional address parameters including: |
| - Cidade (City) | |
| - Complemento (Address complement) | |
| - País (Country) | |
| - Bairro (Neighborhood) | |
| - Número (House number) | |
| - CEP (Postal code) | |
| - Estado (State) | |
| - Rua (Street) |
Output
The node outputs JSON data representing the created boleto event with all the provided input details structured accordingly. This output can be used downstream in workflows for further processing, logging, or integration.
There is no indication that the node outputs binary data.
Dependencies
- Requires an API key credential or similar authentication token to connect to the external service managing events.
- The node likely interacts with an external API endpoint to register the boleto event.
- Proper configuration of credentials and network access in n8n is necessary.
Troubleshooting
- Missing Required Fields: Errors may occur if mandatory fields like "Primeiro Nome", "Telefone", "Produtos", or boleto-specific fields are missing. Ensure all required inputs are provided.
- Invalid Date Format: The "Data De Nascimento" and "Data Do Vencimento Do Boleto" must follow the specified formats (e.g., YYYY-MM-DD). Incorrect formats may cause validation errors.
- API Authentication Failures: If the API key or authentication token is invalid or missing, the node will fail to create the event.
- Network Issues: Connectivity problems to the external API can cause timeouts or failures.
- Incorrect Currency Codes: The "Moeda" field should use valid currency codes (e.g., BRL, USD). Invalid codes might lead to rejection by the API.
Links and References
- Boleto Payment Information — General information about boleto payments.
- ISO 4217 Currency Codes — Standard currency codes reference.
- Documentation of the external API managing boleto events (not provided here).