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). This event typically involves registering or logging details related to a boleto payment slip that has been printed. Such a node would be beneficial in e-commerce or financial automation workflows 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 printed for an order.
- Triggering follow-up actions such as sending reminders or updating order status after boleto printing.
- Integrating boleto event data into CRM or ERP systems for enhanced customer and financial record keeping.
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 |
| 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 |
| Customer's email address | |
| CPF/CNPJ | Customer's document number (CPF or CNPJ) |
| IP | Customer's IP address |
| Produtos | Collection of products involved in the order/event, each with: |
| - Nome Do Produto (Product name) | |
| - Quantidade Do Produto (Product quantity) | |
| - Valor Do Produto (Product value) | |
| Campo Produtos Obrigatório | Notice indicating that product fields are mandatory |
| 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 |
| 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 |
| Linha Digitável Do Boleto | The barcode line of the boleto |
| Valor Do Boleto | Value amount 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 from the source or properties that the node outputs binary data.
Dependencies
- The node likely requires an API key or authentication token to connect to the external service managing boleto events.
- Proper configuration of credentials within n8n is necessary to authenticate requests.
- The node depends on the external system's API that handles event creation for boletos.
Troubleshooting
- Missing Required Fields: Errors may occur if required fields like "Primeiro Nome", "Telefone", "Produtos", or "ID Do Pedido" are not provided. Ensure all mandatory inputs are filled.
- Invalid Date Format: The "Data De Nascimento" and "Data Do Vencimento Do Boleto" must follow the specified formats; otherwise, the API might reject the request.
- Incorrect URLs: The boleto links ("Link Para O Boleto Em HTML" and "Link Para O Boleto Em PDF") should be valid URLs; invalid URLs could cause failures.
- Authentication Failures: If API credentials are missing or incorrect, the node will fail to create events.
- API Rate Limits or Downtime: External service limitations or outages can cause errors; check service status and retry policies.
Links and References
- Boleto Payment Information — General info about boleto payments.
- Documentation for the external API managing boleto events (not provided here, but recommended to consult).
- n8n documentation on creating custom nodes and handling fixed collections for complex inputs.