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 utility payment batches within the Payment resource. Specifically, the "Get" operation for the "Utility Batches" resource retrieves detailed information about a specific utility payment batch by its unique ID.
Common scenarios where this node is beneficial include:
- Fetching details of a particular utility payment batch for auditing or reconciliation.
- Integrating utility payment batch data into workflows for reporting or further processing.
- Automating retrieval of batch status or metadata in financial automation pipelines.
Practical example:
- A finance team wants to automatically retrieve and log the details of a utility payment batch after it has been created or processed, to update their internal systems or notify stakeholders.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the utility payment batch to retrieve. This is a required string input. |
Output
The node outputs a JSON object representing the utility payment batch details as returned by the Kobana API. This typically includes all relevant fields describing the batch such as batch ID, status, creation date, list of payments included, totals, and other metadata.
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
- Missing or invalid ID: The "ID" property is required. If omitted or incorrect, the API will return an error indicating the resource was not found.
- Authentication errors: Ensure that the Kobana API credential is correctly configured and valid.
- API environment mismatch: Using the wrong environment (sandbox vs production) may cause unexpected results or failures.
- Network issues: Connectivity problems can cause request failures; verify network access to the Kobana API endpoints.
- Unexpected API response: If the API changes or returns errors, check the request parameters and consult Kobana API documentation.
Links and References
- Kobana API Documentation (general reference for API endpoints and data structures)
- n8n documentation on Using Credentials