KobanaInstall

Overview

This node interacts with the Kobana API to manage TED transfer batches. Specifically, the "Get Many" operation under the "Transfer > TED Batches" resource allows users to retrieve a list of TED transfer batches from their Kobana account.

This operation is useful when you want to:

• Retrieve multiple TED transfer batch records for reporting or auditing.
• Filter and paginate through TED batches based on query parameters.
• Automate workflows that require processing or analyzing multiple TED batches at once.

For example, a finance team could use this node to fetch all TED batches created in the last month to reconcile payments or generate reports.

Properties

Details:

• Return All: If true, the node will fetch all available TED batches without limiting the number of results.
• Limit: When "Return All" is false, limits the number of TED batches returned to this number.
• Additional Fields: Allows specifying extra fields in JSON format to customize the request.
• Query Parameters: Allows passing arbitrary query parameters as a JSON object to filter or control the API response (e.g., date ranges, status filters).

Output

The output is an array of JSON objects representing TED transfer batches retrieved from the Kobana API.

Each item in the output corresponds to one TED batch and contains all the data fields returned by the API for that batch, such as batch ID, creation date, status, total amount, and other metadata.

No binary data is output by 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.
• No other external dependencies are required.

Troubleshooting

• Common Issues:

  • Incorrect or missing API credentials will cause authentication failures.
  • Providing invalid JSON in "Additional Fields" or "Query Parameters" may cause request errors.
  • Exceeding API rate limits can result in temporary blocking or errors.
  • Using unsupported query parameters may lead to unexpected results or errors.

• Error Messages:

  • Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
  • JSON parsing errors suggest malformed JSON input; ensure valid JSON syntax.
  • HTTP errors from the API (4xx or 5xx) should be checked against Kobana API documentation for specific causes.

Links and References

• Kobana API Documentation (general reference for API endpoints and parameters)
• n8n Documentation on Using Credentials
• n8n Documentation on HTTP Request Node (for understanding API calls)

Note: This summary is based solely on static analysis of the provided source code and property definitions. Runtime behavior and dynamic responses depend on the actual Kobana API and user inputs.