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
The node interacts with the Kobana API to manage "Discharges" under the V1 API version, specifically supporting the "Get Many" operation. This operation retrieves multiple discharge records from the Kobana system, allowing users to fetch either all available discharges or a limited subset based on specified criteria.
This node is beneficial in scenarios where you need to:
- Retrieve a list of discharge records for reporting or auditing.
- Integrate discharge data into workflows for further processing.
- Filter and paginate through large sets of discharge data efficiently.
For example, a finance team could use this node to pull all discharge transactions within a certain period to reconcile accounts or generate summaries.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all discharge records or only up to a given limit. |
| Limit | Maximum number of discharge records to return (applicable only if "Return All" is false). |
| Additional Fields | JSON object containing additional fields to include in the request for extended filtering or options. |
| Query Parameters | JSON object with query parameters to filter or modify the discharge records retrieval. |
Output
The output is a JSON array where each element represents a discharge record retrieved from the Kobana API. Each record contains the details as provided by the API, which typically includes identifiers, status, dates, and other relevant discharge information.
If the node supports binary data output (not indicated here), it would represent associated files or attachments related to discharges, but for this operation, the output is purely JSON data representing discharge entities.
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).
- No additional external dependencies are required beyond the Kobana API access.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Providing invalid JSON in "Additional Fields" or "Query Parameters" may result in request errors.
- Exceeding the maximum allowed limit (100) when "Return All" is false can cause validation errors.
Error Messages:
- Authentication errors typically indicate issues with the API key; verify that the correct key is configured.
- JSON parsing errors suggest malformed JSON input in properties; ensure valid JSON syntax.
- API rate limits or server errors from Kobana should be handled by retrying after some delay or checking API status.
Links and References
- Kobana API Documentation (general reference for endpoints and data structures)
- n8n documentation on Using Credentials
- JSON formatting guides for constructing valid JSON objects in input properties
