KobanaInstall

Overview

This node allows you to interact with the Kobana API specifically for managing payment batches. The "Get" operation under the "Payment > Batches" resource retrieves detailed information about a specific payment batch by its ID. This is useful when you want to fetch the current status, contents, or metadata of a particular payment batch in your financial workflows.

Common scenarios:

• Retrieving details of a payment batch to verify its contents before processing.
• Checking the status or metadata of a batch for reconciliation or reporting.
• Integrating batch payment data into other systems or dashboards.

Practical example:
You have created multiple payment batches and want to retrieve the details of one batch to confirm which payments it includes and its current processing state. Using this node, you provide the batch ID, and it returns all relevant information about that batch.

Properties

Output

The node outputs a JSON object representing the payment batch details as returned by the Kobana API. This typically includes fields such as batch ID, creation date, status, list of payments included in the batch, totals, and other metadata related to the batch.

If the API supports binary data for this resource (not indicated here), it would be summarized accordingly, but for the "Get" operation on payment batches, the output is purely JSON data describing the batch.

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 additional external dependencies beyond the Kobana API and its authentication are needed.

Troubleshooting

• Common issues:

  • Providing an invalid or non-existent batch ID will likely result in an error from the API indicating the resource was not found.
  • Missing or incorrect API credentials will cause authentication failures.
  • Network connectivity issues can prevent the node from reaching the Kobana API endpoint.

• Error messages:

  • "Resource not found" or similar indicates the provided batch ID does not exist; verify the ID.
  • Authentication errors suggest checking the API key or token configuration.
  • JSON parsing errors may occur if the input body or parameters are malformed (less relevant for "Get" operation since no body is sent).

• Resolution tips:

  • Double-check the batch ID input.
  • Ensure the Kobana API credential is correctly set up and has access rights.
  • Test connectivity to the Kobana API endpoints outside n8n if necessary.

Links and References

• Kobana API Documentation (general reference for API endpoints and data structures)
• n8n documentation on Using Credentials for setting up API keys and tokens