Kobana icon

Kobana

Interact with Kobana API - Quick access to common operations
Join our community

Actions215

Overview

This node interacts with the Kobana API to manage bank billet discharges, specifically supporting the "Get Many" operation under the resource "V1 > Bank Billet Discharges". The "Get Many" operation retrieves multiple bank billet discharge records from the Kobana system, allowing users to fetch either all available records or a limited subset based on specified criteria.

Typical use cases include:

  • Retrieving a list of bank billet discharges for reconciliation or reporting.
  • Filtering discharges by specific query parameters such as date ranges or status.
  • Automating workflows that require batch processing or analysis of multiple discharge records.

For example, a finance team could use this node to pull all bank billet discharges within a certain period to verify payments and update accounting systems accordingly.

Properties

Name Meaning
Return All Whether to return all results or only up to a given limit.
Limit Maximum number of results to return (applicable if "Return All" is false).
Additional Fields JSON object with additional fields for the request (optional extra parameters).
Query Parameters JSON object with query parameters to filter or modify the request (e.g., filtering options).

Details:

  • Return All: Boolean flag; if true, the node fetches all matching discharge records without limiting the count.
  • Limit: Number specifying the maximum number of discharge records to retrieve when "Return All" is false. Minimum 1, maximum 100.
  • Additional Fields: Allows passing extra JSON-formatted fields in the request body for operations that support it (not typically used in "Get Many").
  • Query Parameters: Allows specifying JSON-formatted query parameters to filter or customize the retrieval of discharge records (e.g., filtering by date, status).

Output

The node outputs an array of JSON objects representing the bank billet discharge records retrieved from the Kobana API.

  • Each item in the output array corresponds to one discharge record.
  • The structure of each discharge record matches the API's response schema, typically including fields like discharge ID, related bank billet information, dates, amounts, and status.
  • No binary data output is involved in this operation.

Example output snippet (simplified):

[
  {
    "id": "discharge_123",
    "bank_billet_id": "billet_456",
    "amount": 1500,
    "status": "paid",
    "discharge_date": "2024-05-01T12:00:00Z"
  },
  {
    "id": "discharge_124",
    "bank_billet_id": "billet_789",
    "amount": 2000,
    "status": "pending",
    "discharge_date": "2024-05-02T15:30:00Z"
  }
]

Dependencies

  • Requires an active Kobana API credential configured in n8n with appropriate permissions to access bank billet discharge data.
  • The node dynamically selects the API base URL depending on the environment (production or sandbox).
  • Network connectivity to the Kobana API endpoints is necessary.

Troubleshooting

  • Common Issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Exceeding API rate limits may result in errors or throttling.
    • Incorrectly formatted JSON in "Query Parameters" or "Additional Fields" can cause request parsing errors.
    • Requesting more than the allowed limit (max 100) when "Return All" is false will be rejected.

  • Error Messages:

    • Authentication errors: Check that the API key or token is valid and has required scopes.
    • JSON parse errors: Ensure that JSON inputs for query parameters or additional fields are well-formed.
    • HTTP errors (4xx or 5xx): Review the API documentation for error codes and adjust requests accordingly.

Links and References

Discussion