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 manage internal transfers and other financial-related resources. Specifically, for the Transfer > Internal resource with the Get Many operation, it retrieves multiple internal transfer records from the Kobana system.

Typical use cases include:

  • Fetching a list of internal transfers for reconciliation or reporting.
  • Automating workflows that require bulk retrieval of transfer data.
  • Filtering internal transfers based on query parameters such as date ranges, status, or other metadata.

For example, a finance team could use this node to automatically pull all internal transfers made in the last month to generate reports or trigger follow-up actions.

Properties

Name Meaning
Return All Whether to return all internal transfer results or limit the number of returned items.
Limit Maximum number of internal transfer results to return (applicable if Return All is false).
Additional Fields JSON object with additional fields to customize the request (optional).
Query Parameters JSON object with query parameters to filter or modify the list request (e.g., filters).

Details:

  • Return All: Boolean flag; if true, fetches all available internal transfers without pagination.
  • Limit: Number between 1 and 100 specifying how many results to return when not returning all.
  • Additional Fields: Allows passing extra JSON-formatted fields to the API request body if needed.
  • Query Parameters: Allows specifying additional query parameters as a JSON object to refine the search/filter criteria.

Output

The node outputs an array of JSON objects representing internal transfer records retrieved from the Kobana API.

  • Each item in the output corresponds to one internal transfer entry.
  • The structure of each JSON object matches the API response schema for internal transfers, including fields like transfer ID, amount, date, status, and any other metadata provided by the API.
  • 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.
  • Network access to https://api.kobana.com.br (production) or https://api-sandbox.kobana.com.br (sandbox) is required.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication errors.
    • Exceeding API rate limits may result in throttling or temporary blocks.
    • Incorrectly formatted JSON in Additional Fields or Query Parameters can cause request failures.
    • Requesting too many results without enabling "Return All" may lead to incomplete data.

  • Error messages:

    • Authentication errors typically indicate invalid API keys or insufficient permissions.
    • JSON parsing errors suggest malformed JSON input in properties.
    • HTTP errors (4xx or 5xx) indicate issues with the request or server-side problems.

  • Resolutions:

    • Verify and reconfigure the Kobana API credential.
    • Ensure JSON inputs are valid using a JSON validator.
    • Use "Return All" cautiously to avoid large data loads.
    • Check network connectivity and API status.

Links and References

Discussion