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 utility payment batches within a payment system. Specifically, the Payment > Utility Batches resource with the Update operation allows users to update existing utility payment batch records by specifying their ID and providing updated data in JSON format.
Typical use cases include:
- Modifying details of an existing utility payment batch such as batch metadata or payment instructions.
- Automating updates to batches after initial creation, for example, adjusting amounts or adding notes.
- Integrating batch updates into larger workflows that handle utility payments programmatically.
Example: A user has created a utility payment batch but needs to update some fields like due dates or payment references before processing. This node can be used to send the updated information directly to the Kobana API.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the utility payment batch to update. |
| Additional Fields | Optional JSON object containing extra fields to include in the request (flexible usage). |
| Request Body | Required JSON object representing the updated data for the utility payment batch. |
Output
The node outputs the JSON response returned by the Kobana API after performing the update operation. This typically includes the updated utility batch details such as its ID, status, timestamps, and any other relevant fields reflecting the new state.
No binary data output is indicated for this operation.
Dependencies
- Requires an active Kobana API credential configured in n8n for authentication.
- The node communicates with either the production or sandbox Kobana API endpoints depending on the environment setting in the credentials.
- 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 utility batch, the API will return an error. Verify the ID is correct.
- Malformed JSON in Request Body: Ensure the JSON provided in the "Request Body" property is valid and matches the expected schema for utility batch updates.
- Authentication Failures: Confirm that the Kobana API credential is correctly set up and has necessary permissions.
- API Rate Limits or Network Issues: Temporary failures may occur due to rate limiting or connectivity; retrying the operation might help.
- Unexpected API Response: Check if the Kobana API has changed or if additional required fields are missing in the request body.
Links and References
- Kobana API Documentation (general reference for API endpoints and payloads)
- n8n documentation on Using Credentials
- JSON validation tools to verify request body correctness (e.g., https://jsonlint.com/)
