Kobana icon

Kobana

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

Actions215

Overview

This node integrates with the Kobana API to perform various financial commands and operations related to account management, payments, bank slips, subscriptions, webhooks, and more. Specifically, for the Financial > Commands resource with the Create operation, it allows users to create new financial commands by sending a JSON request body to the Kobana API.

Common scenarios where this node is beneficial include automating financial workflows such as creating payment commands, managing transactions, or issuing instructions to financial accounts programmatically within an n8n workflow. For example, a user might automate the creation of a command to initiate a payment or update financial records based on external triggers.

Properties

Name Meaning
Request Body The JSON object representing the request body to send when creating the financial command. This contains all necessary fields as defined by the Kobana API for the create command endpoint.
Additional Fields A JSON object with additional optional fields that can be included in the request to customize the command creation further.

Output

The node outputs the JSON response returned by the Kobana API after creating the financial command. The output is structured as an array of JSON objects, each corresponding to an input item processed. The exact structure depends on the API response but typically includes details about the created command such as its ID, status, timestamps, and any other metadata provided by the API.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active Kobana API credential configured in n8n, which provides authentication tokens or API keys needed to authorize requests.
  • The node dynamically selects the API base URL depending on the environment (production or sandbox).
  • The node uses HTTP methods (POST for create) to interact with the Kobana REST API endpoints.

Troubleshooting

  • Invalid JSON in Request Body or Additional Fields: If the JSON provided in the "Request Body" or "Additional Fields" properties is malformed, the node will throw a parsing error. Ensure valid JSON syntax.
  • Authentication Errors: If the Kobana API credentials are missing, invalid, or expired, the node will fail to authenticate. Verify that the API key or token is correctly set up in n8n credentials.
  • API Endpoint Errors: Errors from the Kobana API (e.g., 4xx or 5xx HTTP responses) will be returned in the node output. Check the error message for details such as missing required fields or invalid parameters.
  • Rate Limits or Quotas: If the API usage exceeds allowed limits, requests may be throttled or rejected. Monitor usage and adjust workflow frequency accordingly.

Links and References

Discussion