Bankerize - Gerenciamento de PropostasInstall

Overview

This node integrates with the Bankerize API to manage proposals. It supports various operations such as retrieving proposal data, canceling proposals, sending proposals for disbursement, renewing signature links, updating payment account details, and fetching detailed proposal information.

Typical use cases include:

• Automatically fetching the status or details of a specific proposal by its unique identifier.
• Canceling proposals when a client withdraws or an operation is aborted.
• Sending approved proposals to the disbursement process.
• Renewing signature links if clients need a new signing URL.
• Updating bank account information related to a proposal’s payment.
• Retrieving comprehensive details about a proposal for reporting or auditing.

For example, a financial institution could use this node to automate the workflow of loan proposals: checking their status, updating payment info, or canceling them based on business logic.

Properties

Note: This property is required for the "Get Proposal" operation and several others like canceling or updating proposals.

Output

The node outputs JSON data representing the response from the Bankerize API for the requested operation. The structure varies depending on the operation but generally includes:

• For "Get Proposal": JSON object with proposal data fields.
• For "Cancel Proposal", "Send to Disburse", "Renew Signature Link", "Update Payment Account", and "Get Proposal Details": JSON objects confirming the action or returning updated proposal information.
• If no results are found, the output contains a message indicating "Nenhum resultado encontrado." ("No results found").
• In case of errors, the output JSON includes error details such as HTTP status, message, and any returned data.

The node does not output binary data.

Dependencies

• Requires an API key credential for authenticating with the Bankerize API.
• The node uses OAuth2 client credentials flow to obtain access tokens.
• Network access to Bankerize API endpoints is necessary.
• No additional external dependencies beyond standard HTTP requests.

Troubleshooting

• Missing or invalid UUID: Many operations require a valid proposal UUID. Errors will be thrown if this is missing or empty.
• Invalid input formats: For example, CPF must have exactly 11 digits; email must be valid format; phone numbers must have 10 or 11 digits.
• API authentication failures: If the API key or credentials are incorrect or expired, authentication errors will occur.
• Unknown operation: If an unsupported operation name is provided, the node throws an error indicating the operation is unknown.
• Empty results: Some queries may return no data; the node outputs a message indicating no results were found.
• To resolve errors, verify all required parameters are correctly set, ensure credentials are valid, and check network connectivity.

Links and References

• Bankerize API documentation (not included here, but users should consult Bankerize official docs for detailed API specs)
• n8n documentation on creating and using custom nodes and credentials