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 update an existing bank billet batch export resource. Specifically, the "Update" operation under the "V1 > Bank Billet Batch Exports" resource allows users to modify details of a bank billet batch export by providing its ID and the updated data in JSON format.
Common scenarios where this node is beneficial include:
- Adjusting export parameters or metadata for a batch of bank billets after creation.
- Correcting or adding information to an existing bank billet batch export.
- Automating updates to batch exports as part of a larger financial workflow.
Practical example:
- A user has created a bank billet batch export but needs to update some fields such as export settings or descriptions before finalizing it. Using this node, they can specify the batch export ID and provide the new data in JSON to update the resource seamlessly.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the bank billet batch export to update (required). |
| Additional Fields | Optional JSON object containing extra fields to include in the request for customization. |
| Request Body | The main JSON payload representing the updated data for the bank billet batch export (required). |
Output
The node outputs the JSON response returned by the Kobana API after performing the update operation. This typically includes the updated representation of the bank billet batch export resource, reflecting all changes made.
If the API returns binary data (not typical for update operations), it would represent file contents or export data related to the batch export, but this operation primarily deals with JSON data.
Dependencies
- Requires an active Kobana API credential configured in n8n with appropriate permissions to update bank billet batch exports.
- The node dynamically selects the API base URL depending on whether the environment is production or sandbox.
- No additional external dependencies are required beyond the Kobana API access.
Troubleshooting
- Invalid ID error: If the provided ID does not correspond to an existing bank billet batch export, the API will return an error. Verify that the ID is correct.
- Malformed JSON in Request Body: Ensure the JSON provided in the "Request Body" field is valid and correctly formatted; otherwise, the request will fail.
- Insufficient Permissions: The API key used must have rights to update bank billet batch exports; otherwise, authorization errors will occur.
- Network or API Endpoint Issues: Confirm network connectivity and that the correct environment (production vs sandbox) is selected in credentials.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output.
Links and References
- Kobana API Documentation (general reference for API endpoints and data structures)
- n8n documentation on creating custom nodes for further customization guidance
