Bankerize - Gerenciamento de Propostas
Actions8
Overview
This node integrates with the Bankerize API to manage proposals. 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 Cancel Proposal operation specifically allows users to cancel an existing proposal by providing its unique identifier (UUID) and optionally specifying a reason for cancellation.
Typical use cases include:
- Automating the cancellation of loan or credit proposals when clients withdraw.
- Integrating proposal management into larger workflows that handle client requests or status updates.
- Maintaining up-to-date proposal statuses in external systems by syncing cancellations.
Example: A financial institution can automatically cancel a loan proposal if a customer decides not to proceed, recording the cancellation reason for audit purposes.
Properties
| Name | Meaning |
|---|---|
| UUID Da Proposta | The unique UUID of the proposal to be canceled. This is required to identify the proposal. |
| Motivo Do Cancelamento | Optional text describing the reason for canceling the proposal (e.g., "Client withdrew"). |
Output
The output JSON contains the response from the Bankerize API after attempting to cancel the proposal. This typically includes confirmation of the cancellation or error details if the operation failed.
If no data is returned by the API, the node throws an error indicating the operation did not return data.
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 within n8n is necessary.
- Network access to Bankerize's API endpoints must be available.
Troubleshooting
- Missing UUID: If the UUID of the proposal is not provided or empty, the node will throw an error stating that the UUID is mandatory.
- Invalid API Credentials: Authentication failures will result in errors; ensure the API key credential is correctly configured.
- API Errors: If the Bankerize API returns an error (e.g., invalid UUID, proposal already canceled), the node will propagate this error message.
- Empty Response: If the API does not return any data, the node throws an error indicating no data was returned for the cancel operation.
- Network Issues: Connectivity problems may cause request failures; verify network access and endpoint availability.
To resolve errors:
- Verify all required parameters are set and valid.
- Check API credentials and permissions.
- Review the cancellation reason format if provided.
- Consult Bankerize API documentation for specific error codes.
Links and References
- Bankerize API Documentation (general reference): https://bankerize.com.br/api-docs (hypothetical link)
- n8n HTTP Request Node Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
- Best practices for API authentication in n8n: https://docs.n8n.io/credentials/api-key/