Bankerize - E-Consignado
Actions5
Overview
The "Create Proposal" operation of the Bankerize - E-Consignado node allows users to create a new loan proposal for private payroll-deductible loans (consignado privado) via the Bankerize API. This operation collects detailed personal, contact, address, bank account, simulation, and employment relationship data about a client and submits it to the API to generate a formal proposal.
This node is beneficial in financial services automation where loan proposals need to be created programmatically based on prior simulations and verified employment data. For example, a financial institution or broker can automate the creation of loan proposals after validating a client's employment and simulating loan terms, streamlining the credit approval process.
Practical use cases include:
- Automating loan proposal submissions after client data collection.
- Integrating with CRM systems to push loan proposals directly to Bankerize.
- Batch processing multiple clients' loan proposals using workflow automation.
Properties
| Name | Meaning |
|---|---|
| Dados Pessoais | Notice section header for personal client information |
| Nome Completo | Full name of the client (required) |
| CPF | Client's CPF number (Brazilian individual taxpayer registry, 11 digits, required) |
| Data De Nascimento | Client's birth date in DD/MM/YYYY format (required) |
| Sexo | Client's gender ("M" or "F", required) |
| Estado Civil | Client's civil status (e.g., SOLTEIRO, CASADO, DIVORCIADO, VIUVO, UNIAO_ESTAVEL, required) |
| Escolaridade | Client's education level (e.g., ENSINO_FUNDAMENTAL, ENSINO_MEDIO, SUPERIOR_COMPLETO, etc.) |
| Número Do RG | Client's RG number (optional, Brazilian identity card number) |
| Órgão Emissor RG | Issuing authority of RG (optional) |
| UF Do RG | State issuing the RG (optional) |
| Dados de Contato | Notice section header for client contact information |
| Client's email address (optional) | |
| Celular | Client's cellphone number (only numbers, required) |
| Endereço | Notice section header for client address |
| CEP | Postal code (CEP) of client address (only numbers, required) |
| Rua/Logradouro | Street or public place name (required) |
| Bairro | Neighborhood (required) |
| Estado (UF) | State abbreviation (e.g., SP) (required) |
| Número | Address number (required) |
| Complemento | Address complement (optional) |
| Cidade | City name (required) |
| Dados Bancários | Notice section header for bank account details |
| Código Do Banco | Bank code (e.g., 001, 237, 341) (required) |
| Tipo De Conta | Bank account type (e.g., Conta Corrente, Conta Poupança, Conta Pagamento) (required) |
| Agência | Bank agency number without digit (required) |
| Dígito Da Agência | Agency check digit (optional) |
| Número Da Conta | Bank account number without digit (required) |
| Dígito Da Conta | Account check digit (required) |
| Dados da Simulação | Notice section header for chosen simulation ID |
| ID Da Simulação | UUID of the simulation obtained from a previous operation (required) |
| Vínculo Empregatício | Notice section header for chosen employment relationship |
| Request UUID | UUID received from employment relationships query (required) |
| Matrícula | Registration number of the chosen employment relationship (required) |
Output
The output JSON contains the response from the Bankerize API after creating the proposal. It typically includes confirmation details of the created proposal such as IDs, status, and any relevant metadata returned by the API.
If an error occurs, the output JSON will contain error details including HTTP status, message, and possibly additional data explaining the failure.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Bankerize API.
- The node uses the Bankerize API endpoints for E-Consignado operations.
- Proper configuration of the API credentials within n8n is necessary.
- The node expects valid UUIDs and properly formatted Brazilian-specific data (CPF, CNPJ, CEP, dates).
Troubleshooting
- Missing Required Fields: Errors will occur if mandatory fields like CPF, customer name, simulation ID, request UUID, or registration are missing or empty.
- Invalid CPF Format: CPF must be exactly 11 digits; otherwise, the node throws an error.
- Date Format Issues: Birth date must be in DD/MM/YYYY format; incorrect formats may cause errors.
- API Authentication Failures: Ensure the API key credential is correctly set up and has proper permissions.
- Network or API Errors: The node captures HTTP errors and returns structured error messages. Check network connectivity and API service status.
- Continue On Fail Behavior: If enabled, errors are returned as part of the output JSON instead of stopping execution.
Links and References
- Bankerize API Documentation (general reference, actual URL may vary)
- Brazilian CPF validation rules: https://en.wikipedia.org/wiki/Cadastro_de_Pessoas_F%C3%ADsicas
- Brazilian postal codes (CEP): https://en.wikipedia.org/wiki/Postal_codes_in_Brazil