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 payment bank billets (bank slips). Specifically, the Update operation for the Payment > Bank Billets resource allows users to modify existing bank billet records by sending updated data to the API. This is useful in scenarios where details of a bank slip need correction or adjustment after creation, such as changing due dates, amounts, or payer information.
Practical examples include:
- Updating the amount or due date of an issued bank slip.
- Correcting customer information linked to a bank slip.
- Adjusting payment instructions or other metadata associated with the bank slip.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the bank billet to update. |
| Request Body | 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 required for update). |
Output
The node outputs the JSON response returned by the Kobana API after updating the bank billet. This JSON typically contains the updated bank billet data reflecting the changes made.
- The output is structured as an array of JSON objects, each representing the updated bank billet.
- No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Kobana API.
- The node dynamically selects the API base URL depending on the environment (production or sandbox).
- Proper configuration of the Kobana API credentials in n8n is necessary.
Troubleshooting
- Invalid ID error: If the provided bank billet ID does not exist or is malformed, the API will return an error. Verify the ID before running the node.
- Malformed JSON in Request Body: The "Request Body" must be valid JSON. Invalid JSON syntax will cause parsing errors. Use a JSON validator if needed.
- Authentication errors: Ensure that the API key credential is correctly set up and has permissions to update bank billets.
- API rate limits or downtime: Temporary failures may occur if the Kobana API is unavailable or rate-limited. Retry later or check API status.
Links and References
- Kobana API Documentation (general reference for API endpoints and payloads)
- n8n documentation on HTTP Request Node for understanding how API calls are made within nodes
