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 allows you to interact with the Kobana API specifically for managing Payment Batches. The "Update" operation lets you modify an existing payment batch by specifying its ID and providing a JSON request body with the fields to update.
Typical use cases include:
- Adjusting details of a payment batch after creation, such as changing metadata or updating batch parameters.
- Automating batch updates in workflows that manage multiple payments.
- Integrating batch management into larger financial automation processes.
For example, you might update a batch’s description or status based on external triggers or after validating payment information.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the payment batch you want to update. |
| Request Body | A JSON object containing the fields and values to update in the payment batch. |
| 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 after performing the update operation. This JSON contains the updated payment batch data, reflecting any changes made.
The output is structured as an array of JSON objects, each representing the updated batch information corresponding to each input item processed.
No binary data output is involved in this operation.
Dependencies
- Requires an active Kobana API credential configured in n8n with appropriate permissions.
- The node dynamically selects the API base URL depending on whether the environment is production or sandbox.
- The request uses standard HTTP methods and expects JSON-formatted request bodies and responses.
Troubleshooting
- Invalid ID error: If the provided batch ID does not exist or is malformed, the API will return an error. Verify the ID before running the update.
- Malformed JSON in Request Body: Ensure the JSON provided in the "Request Body" field is valid. Invalid JSON will cause parsing errors.
- Permission issues: Make sure the API key has rights to update payment batches.
- API environment mismatch: Confirm if you are targeting the correct environment (production vs sandbox) as per your credentials.
- Continue On Fail: If enabled, the node will continue processing other items even if one fails, returning error details in the output JSON.
Links and References
- Kobana API Documentation (general reference for endpoints and payloads)
- n8n documentation on Using Credentials
- JSON validation tools (e.g., https://jsonlint.com/) to verify request body correctness
