Ksaar icon

Ksaar

Consume Ksaar API

Actions13

Overview

This node interacts with the Ksaar API to retrieve information about applications. Specifically, the "Applications" resource with the "Get" operation allows users to fetch a list of applications from Ksaar. It supports pagination and sorting, enabling users to either retrieve all applications or a subset based on page number and results per page.

Common scenarios where this node is beneficial include:

  • Automating workflows that require fetching application data for reporting or processing.
  • Integrating Ksaar application data into other systems or dashboards.
  • Periodically syncing application lists from Ksaar to keep external databases up to date.

For example, a user might use this node to get all applications sorted by creation date to generate a report of newly created applications in their Ksaar account.

Properties

Name Meaning
Send Headers Whether to send custom HTTP headers with the request (true/false).
Headers If "Send Headers" is true, specify one or more HTTP headers as key-value pairs.
Return All Whether to return all application results by automatically paginating through all pages.
Results per Page Number of application results to return per page when not returning all (1 to 500).
Page Number The page number to retrieve when not returning all results (minimum 1).
Sort By Field to sort the applications by; options are "Created At" or "Updated At".

Output

The node outputs an array of application objects in the json output field. Each object represents an application retrieved from Ksaar and contains its associated data fields as returned by the Ksaar API.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Ksaar API via an API authentication token configured in n8n credentials.
  • The node makes HTTP GET requests to the Ksaar API endpoint at https://api.ksaar.co/v1/applications.
  • Optional: Custom HTTP headers can be sent if enabled.

Troubleshooting

  • Empty results or no data returned:
    Ensure that the API credentials are valid and have permission to access application data. Also, verify that the requested page number and results per page parameters are within valid ranges.

  • API rate limits or timeouts:
    When retrieving all results (Return All enabled), large datasets may cause delays or hit API rate limits. Consider using pagination with smaller page sizes.

  • Invalid parameter values:
    Parameters like "Results per Page" must be between 1 and 500, and "Page Number" must be at least 1. Invalid values will likely cause API errors.

  • Custom headers not applied:
    If "Send Headers" is enabled but headers are not sent, verify that headers are correctly defined as name-value pairs.

Links and References

Discussion