Bankerize - FGTS icon

Bankerize - FGTS

Gerenciar operações FGTS da API Bankerize: simular propostas (incluindo por parcelas), criar propostas e consultar status. Use para realizar operações de antecipação do Saque-Aniversário FGTS.
Join our community

Actions4

Overview

This node integrates with the Bankerize API to manage FGTS (Fundo de Garantia do Tempo de Serviço) operations. Specifically, it allows users to create FGTS loan proposals based on a previously simulated proposal ID. The node collects detailed personal, contact, address, bank account, and subscriber information to submit a formal loan proposal request.

Common scenarios for this node include automating the creation of FGTS loan proposals in financial workflows, integrating client data collection with Bankerize’s FGTS services, and streamlining loan origination processes that require precise customer and banking details.

For example, a financial institution can use this node to automatically generate loan proposals after simulating terms, ensuring all required client and banking data is validated and submitted correctly to Bankerize.

Properties

Name Meaning
Simulation ID The ID of the chosen FGTS simulation to base the proposal on.
Dados Pessoais Notice section prompting to fill in the client's personal data.
Nome Completo Full name of the client.
CPF Client's CPF number (Brazilian individual taxpayer registry identification), digits only.
Data De Nascimento Client's birth date. Accepts formats DD/MM/YYYY, MM/DD/YYYY, or YYYY-MM-DD. Automatically converted to YYYY-MM-DD.
Gênero Client's gender. Options: Masculino (M), Feminino (F).
Estado Civil Client's marital status. Options: Solteiro(a), Casado(a), Divorciado(a), Separado(a), Viúvo(a), Outros.
Escolaridade Client's education level. Options range from Maternal Incompleto to Ensino Superior Completo.
Número Do RG Client's RG number (general Brazilian identity document).
Órgão Emissor Do RG Issuing authority of the RG (e.g., SSP).
UF Do RG State where the RG was issued (e.g., SP).
Contatos Notice section for client contact information.
Email Client's email address.
Celular Client's cellphone number (digits only, e.g., 11987654321).
Endereço Notice section for residential address.
CEP Postal code (digits only, exactly 8 digits).
Rua Street or logradouro name.
Número Address number.
Complemento Address complement (apartment, house, etc.). Optional.
Bairro Neighborhood.
Cidade City.
UF State abbreviation (UF), e.g., SP, RJ, MG.
Dados Bancários Notice section for bank account details where funds will be credited.
Código Do Banco Bank code (e.g., 237 for Bradesco, 1 for Banco do Brasil).
Tipo De Conta Bank account type. Options: Conta Corrente (CCT), Conta Poupança (CPP), Conta Pagamento (CPG).
Agência Bank agency number (without digit).
Dígito Da Agência Agency verification digit. Optional.
Número Da Conta Bank account number (without digit).
Dígito Da Conta Account verification digit.
Valor Split Commission or split value amount.
Assinantes Notice section for loan signatories' data.
CPF Do Assinante Signatory's CPF number (digits only).
Nome Do Assinante Full name of the signatory.
Email Do Assinante Signatory's email address.
Telefone Do Assinante Signatory's phone number with area code (digits only, e.g., 11999999999).

Output

The node outputs JSON data representing the response from the Bankerize API after attempting to create an FGTS proposal. This includes:

  • Confirmation of the created proposal with relevant identifiers and status.
  • Error messages if the creation failed, including HTTP status codes and descriptive messages.
  • Structured data reflecting the submitted proposal details and any returned metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authentication with the Bankerize API.
  • The node uses HTTP requests to interact with Bankerize endpoints.
  • No additional external dependencies beyond the Bankerize API and n8n core modules are needed.
  • Proper configuration of the API credentials within n8n is necessary.

Troubleshooting

  • Missing or invalid required fields: The node performs strict validation on inputs such as CPF length (must be exactly 11 digits), valid email format, phone number length (minimum 10 digits), and date formatting. Errors will be thrown if these validations fail.
  • Date format errors: Birth dates must be in accepted formats and convertible to YYYY-MM-DD. Invalid dates cause errors.
  • API errors: If the Bankerize API returns an error, the node captures and outputs the status code, message, and any error data. Common issues include invalid simulation IDs or authorization failures.
  • Empty or malformed JSON arrays: For example, the subscribers array must contain at least one valid subscriber with all required fields.
  • Phone number formatting: Phone numbers are cleaned to digits only and must have 10 or 11 digits; otherwise, errors occur.
  • To resolve errors, ensure all required fields are correctly filled, formatted, and validated before execution.

Links and References

If you need further details about other operations or resources, feel free to ask!

Discussion