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 interacts with the Kobana API to manage bank billet discharges, specifically allowing you to update existing bank billet discharge records. Bank billet discharges typically represent the process of marking a bank slip (boleto) as discharged or settled in the system.
The Update operation for "V1 > Bank Billet Discharges" enables users to modify details of a specific bank billet discharge by providing its ID and the updated data in JSON format.
Common scenarios:
- Correcting or adding information to an existing bank billet discharge record.
- Updating status or metadata related to a bank billet discharge after receiving new information.
- Automating updates to bank billet discharges based on external triggers or workflows.
Practical example:
You have a workflow that receives payment confirmation from a financial system and needs to update the corresponding bank billet discharge record with additional payment details or status changes.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the bank billet discharge to update. |
| Request Body | A JSON object containing the fields and values to update in the bank billet discharge. |
| Additional Fields | Optional JSON object with extra fields to include in the request (not mandatory). |
Output
The node outputs the JSON response returned by the Kobana API after updating the bank billet discharge. This typically includes the updated discharge record details such as IDs, status, timestamps, and any other relevant fields returned by the API.
If the API supports binary data output for this resource (not indicated here), it would be summarized accordingly, but in this case, the output is purely JSON data representing the updated resource.
Dependencies
- Requires an active Kobana API credential configured in n8n with appropriate permissions.
- The node dynamically selects the API base URL depending on the environment (production or sandbox).
- The node uses HTTP methods (PUT) to send update requests to the Kobana API endpoint
/v1/bank_billet_discharges/{id}.
Troubleshooting
- Invalid ID error: Ensure the provided ID corresponds to an existing bank billet discharge in the Kobana system.
- Malformed JSON in Request Body: The
Request Bodymust be valid JSON. Invalid JSON will cause the request to fail. - Authentication errors: Verify that the Kobana API credentials are correctly set up and have sufficient permissions.
- API environment mismatch: Confirm whether you are targeting production or sandbox environment and use the correct credentials.
- Network or timeout issues: Check network connectivity and API availability if requests fail unexpectedly.
Links and References
- Kobana API Documentation (general reference for endpoints and payloads)
- n8n documentation on Using Credentials
- JSON formatting guide for constructing valid request bodies: https://www.json.org/json-en.html
