Bankerize - Gerenciamento de Propostas
Actions8
Overview
This node integrates with the Bankerize API to manage proposals and related operations. Specifically, for the "Request Query Authorization" operation, it allows users to request authorization for querying client data in operations that require explicit client consent. This is useful in scenarios where compliance with data privacy or consent regulations is necessary before accessing sensitive client information.
Practical examples include:
- Requesting a client's authorization before performing credit checks.
- Obtaining consent for querying financial data related to loan or credit proposals.
- Automating the process of sending authorization requests via email and SMS to clients.
Properties
| Name | Meaning |
|---|---|
| Dados do Cliente | Informational notice about the required client data to request query authorization. |
| CPF | Client's CPF number (Brazilian individual taxpayer registry identification), digits only. |
| Nome Completo | Full name of the client. |
| Client's email address to send the authorization request. | |
| Celular | Client's mobile phone number, digits only, used for contact regarding authorization. |
| Tipo De Operação | Type of operation requiring authorization; currently supports "E-Consignado" only. |
Output
The node outputs JSON data representing the response from the Bankerize API after requesting query authorization. The structure typically includes confirmation details of the authorization request or error messages if the request fails.
No binary data output is produced by this operation.
Example JSON output might look like:
{
"id": "authorization-request-id",
"status": "pending",
"message": "Authorization request sent successfully"
}
Or, in case of no results or errors:
{
"message": "Nenhum resultado encontrado."
}
or
{
"error": "Error message details"
}
Dependencies
- Requires an API key credential for authenticating with the Bankerize API.
- The node uses HTTP requests to communicate with Bankerize endpoints.
- Proper configuration of the API credentials within n8n is necessary.
- Network access to Bankerize API endpoints must be available.
Troubleshooting
- Missing or invalid CPF: The CPF must be exactly 11 digits long and contain only numbers. Errors will occur if this validation fails.
- Invalid email format: The email must be valid; otherwise, the node throws an error.
- Invalid cellphone number: The cellphone number must have 10 or 11 digits, digits only.
- API authentication errors: Ensure the API key credential is correctly configured and has proper permissions.
- Unknown operation error: If an unsupported operation is selected, the node will throw an error indicating the operation is unknown.
- Empty or missing required parameters: The node validates required fields and will throw errors if any are missing or empty.
To resolve these issues:
- Double-check all input fields for correct formatting and completeness.
- Verify API credentials and network connectivity.
- Review error messages returned by the node for specific guidance.
Links and References
- Bankerize API Documentation (general reference for API endpoints)
- CPF Validation Rules
- Email Format Validation
- n8n Documentation on Creating Custom Nodes