Actions215
- V1 > Bank Billets Actions
- V1 > Bank Billet Accounts Actions
- V1 > Bank Billet Batches Actions
- V1 > Bank Billet Batch Exports Actions
- V1 > Bank Billet Discharges Actions
- V1 > Bank Billet Payments Actions
- V1 > Bank Billet Registrations Actions
- V1 > Bank Billet Remittances Actions
- V1 > Customers Actions
- V1 > Customer Subscriptions Actions
- V1 > Discharges Actions
- V1 > Email Deliveries Actions
- V1 > Events Actions
- V1 > Imports Actions
- V1 > Installments Actions
- V1 > Remittances Actions
- V1 > Reports Actions
- V1 > SMS Deliveries Actions
- V1 > User Info Actions
- V1 > Webhook Deliveries Actions
- V1 > Webhooks Actions
- Admin > Users Actions
- Admin > Connections Actions
- Admin > Certificates Actions
- Admin > Subaccounts Actions
- Charge > PIX Actions
- Charge > PIX Accounts Actions
- Data > Bank Billet Queries Actions
- EDI > EDI Boxes Actions
- Financial > Accounts Actions
- Financial > Balances Actions
- Financial > Commands Actions
- Financial > Statement Transactions Actions
- Financial > Transaction Imports Actions
- Financial > Providers Actions
- Payment > Bank Billets Actions
- Payment > Bank Billet Batches Actions
- Payment > Batches Actions
- Payment > DARFs Actions
- Payment > DARF Batches Actions
- Payment > PIX Actions
- Payment > PIX Batches Actions
- Payment > Utilities Actions
- Payment > Utility Batches Actions
- Transfer > Batches Actions
- Transfer > Internal Actions
- Transfer > Internal Batches Actions
- Transfer > PIX Actions
- Transfer > PIX Batches Actions
- Transfer > TED Actions
- Transfer > TED Batches Actions
Overview
This node integrates with the Kobana API to manage bank billets (bank slips) specifically under the "V1 > Bank Billets" resource. The Update operation allows users to modify an existing bank billet by specifying its ID and providing a JSON request body with the updated data.
Typical use cases include:
- Correcting or updating details of a previously created bank slip, such as due dates, amounts, or payer information.
- Automating updates to bank billets in workflows where payment terms or customer data change.
- Integrating with financial systems to keep bank slip records synchronized.
Example: Updating the due date or amount of a bank billet after negotiation with a customer.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the bank billet to update. |
| Request Body | A JSON object containing the fields and values to update on the bank billet. |
| Additional Fields | Optional JSON object with extra fields for the request (not typically used in update). |
Output
The node outputs the JSON response from the Kobana API representing the updated bank billet. This JSON includes all relevant details of the bank billet after the update, such as IDs, status, amounts, dates, and any other properties returned by the API.
No binary data output is involved in this operation.
Dependencies
- Requires an active Kobana API credential configured in n8n for authentication.
- The node dynamically selects the API base URL depending on whether the environment is production or sandbox.
- The request uses HTTP PUT method to the endpoint
/v1/bank_billets/{id}with the provided JSON body.
Troubleshooting
- Invalid ID error: If the specified bank billet ID does not exist or is malformed, the API will return an error. Verify the ID correctness.
- Malformed JSON in Request Body: Ensure the JSON provided in the "Request Body" property is valid and matches the expected schema for bank billet updates.
- Authentication errors: Confirm that the Kobana API credentials are correctly set up and have permissions to update bank billets.
- API environment mismatch: Make sure you are using the correct environment (production vs sandbox) matching your API key.
- Network issues: Check connectivity to the Kobana API endpoints if requests time out or fail.
Links and References
- Kobana API Documentation (general reference for API endpoints and payloads)
- n8n documentation on Using Credentials
- JSON formatting tools to validate request bodies before use
