Bankerize - Gerenciamento de Propostas
Actions8
Overview
This node integrates with the Bankerize API to manage proposals related to financial operations. It supports multiple operations such as canceling a proposal, retrieving proposal data, sending a proposal for disbursement, renewing signature links, updating payment account details, and more.
The Update Payment Account operation specifically allows users to update the bank account information associated with a given proposal. This is useful when the payment details need to be changed or corrected after the proposal has been created.
Practical examples:
- A financial institution automates updating client bank details for loan disbursements.
- An operations team corrects payment account information without manual intervention.
- Automating workflows that require keeping payment data synchronized between systems.
Properties
| Name | Meaning |
|---|---|
| UUID Da Proposta | Unique identifier (UUID) of the proposal to update. |
| Dados Bancários | Informational notice prompting the user to update bank account details for the proposal. |
| Código Do Banco | Bank code number (e.g., 237 for Bradesco, 001 for Banco do Brasil). |
| Tipo De Conta | Type of bank account. Options: "Conta Corrente" (Checking Account), "Conta Poupança" (Savings Account), "Conta Pagamento" (Payment Account). |
| Agência | Bank agency number. |
| Dígito Da Agência | Optional check digit for the bank agency number. |
| Número Da Conta | Bank account number. |
| Dígito Da Conta | Check digit for the bank account number. |
Output
The output JSON contains the response from the Bankerize API after attempting to update the payment account information for the specified proposal. The structure depends on the API's response but generally includes confirmation of the update or error details.
If no results are found or an error occurs, the output will contain a message or error object describing the issue.
No binary data output is produced by this operation.
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 in n8n is necessary.
- Network access to Bankerize API endpoints must be available.
Troubleshooting
- Missing or invalid UUID: The node requires a valid proposal UUID; missing or empty values will cause errors.
- Invalid bank codes or account details: Ensure all required bank fields are correctly filled; missing mandatory fields like bank code, agency, account number, or digits will trigger errors.
- API authentication failures: Incorrect or expired API credentials will prevent successful requests.
- Unexpected API responses: If the API returns errors, the node captures and outputs these in the JSON for diagnosis.
- Validation errors: For example, if required parameters are empty or malformed, the node throws descriptive errors.
To resolve issues:
- Double-check all required input fields.
- Verify API credentials and permissions.
- Review error messages returned in the node output for specific causes.
Links and References
- Bankerize API Documentation (Assumed URL based on context; replace with actual if known)
- n8n Documentation on Creating Custom Nodes
- General info on UUIDs: https://en.wikipedia.org/wiki/Universally_unique_identifier