Bankerize - Gerenciamento de Propostas
Actions8
Overview
This node integrates with the Bankerize API to manage proposals. It supports various operations such as retrieving detailed information about a proposal, canceling a proposal, sending it for disbursement, renewing signature links, updating payment account details, and more.
The Get Proposal Details operation fetches comprehensive details of a specific proposal identified by its unique UUID. This is useful when you need an in-depth view of a proposal's current state and associated data within your workflow.
Practical examples:
- Automatically retrieve full proposal details after a user submits a form to verify all information before approval.
- Use detailed proposal data to trigger conditional logic or notifications in your automation.
- Audit or log proposal details periodically for compliance or reporting purposes.
Properties
| Name | Meaning |
|---|---|
| UUID Da Proposta | The unique UUID identifier of the proposal to be detailed. This is required. |
Output
The node outputs JSON data representing the detailed information of the specified proposal. The structure corresponds directly to the response from the Bankerize API's proposal detailing endpoint. It typically includes all relevant fields describing the proposal's status, client data, financial details, signatures, and other metadata.
If no data is found, the output will contain 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.
- No additional environment variables are explicitly required beyond the API credentials.
Troubleshooting
- Missing or invalid UUID: The node requires a valid UUID string for the proposal. If omitted or empty, it throws an error stating the UUID is mandatory.
- API authentication errors: Ensure the provided API credentials are correct and have sufficient permissions.
- Network or API errors: Errors returned from the Bankerize API are captured and presented in the output JSON under
status,statusText, andmessagefields. - Empty results: If the proposal UUID does not correspond to any existing proposal, the node returns a message indicating no results were found.
- Invalid email or CPF formats: For other operations (not this one), input validation errors may occur; ensure inputs conform to expected formats.
Links and References
- Bankerize API Documentation (general reference for API endpoints)
- n8n Documentation on Creating Custom Nodes