Bankerize - Gerenciamento de Propostas
Actions8
Overview
This node integrates with the Bankerize API to manage proposals and related operations. Specifically, the "Update Antifraud Status" operation allows users to update the antifraud status of a signature associated with a proposal by providing the signature's UUID and the new status (approved or rejected).
Common scenarios for this node include automating the management of loan or credit proposals, updating antifraud checks after manual or automated review, and integrating antifraud decision workflows into broader automation pipelines.
Practical example: After an antifraud system reviews a customer's signature on a loan proposal, this node can be used to update the status to "approved" or "rejected" in Bankerize, triggering subsequent steps such as disbursement or cancellation.
Properties
| Name | Meaning |
|---|---|
| UUID Da Assinatura | The unique identifier (UUID) of the signature whose antifraud status you want to update. |
| Novo Status | The new antifraud status to set. Options: "Aprovado" (approved), "Rejeitado" (rejected). |
Output
The node outputs JSON data representing the response from the Bankerize API after attempting to update the antifraud status. This typically includes confirmation of the update or details about the updated signature status.
If the operation returns no data, the node outputs a message indicating "Nenhum resultado encontrado." ("No results found.").
The node does not output binary data.
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.
- The node expects the Bankerize API base URL and authentication token, which it obtains internally using client credentials flow.
Troubleshooting
- Missing or invalid UUID: If the UUID of the signature is missing or empty, the node will throw an error stating that the UUID is required. Ensure the UUID is correctly provided.
- Invalid status value: The new status must be either "approved" or "rejected". Providing any other value will cause an error.
- API errors: Network issues, invalid credentials, or API downtime may cause errors. The node attempts to provide detailed error messages including HTTP status codes and messages.
- Continue on Fail: If enabled, the node will continue processing remaining items even if some fail, returning error details in the output JSON.
Links and References
- Bankerize API Documentation (general): https://bankerize.com.br/api-docs (assumed; replace with actual link if available)
- n8n HTTP Request Node Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
- OAuth2 Client Credentials Flow: https://oauth.net/2/grant-types/client-credentials/
This summary focuses exclusively on the "Update Antifraud Status" operation of the Bankerize Proposals node as requested.