Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Integrator Schedule → List Of Integrator Schedule

AI-generated

Overview

This node integrates with the Halo PSA API to list integrator schedules. It allows users to retrieve paginated lists of schedules configured in the Halo PSA system, which can be useful for automation workflows that need to process or analyze scheduled tasks or events managed by Halo PSA.

Typical use cases include:

  • Fetching a specific page of integrator schedules for reporting or monitoring.
  • Automating synchronization of schedule data with other systems.
  • Triggering downstream processes based on schedule information retrieved from Halo PSA.

Properties

Name Meaning
Page No The page number of the results to retrieve (pagination).
Page Size The number of items per page to return (pagination).
Pageinate A query parameter likely controlling pagination behavior (exact meaning depends on API).

These properties are sent as query parameters in the API request to control pagination of the integrator schedule list.

Output

The node outputs an array of JSON objects representing integrator schedules returned by the Halo PSA API. Each item corresponds to one schedule entry as provided by the API response.

The output is structured as:

[
  {
    "json": {
      // Integrator schedule fields as returned by the API
    },
    "pairedItem": {
      "item": <index_of_input_item>
    }
  }
]

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Halo PSA API.
  • The node expects configuration of base URL, tenant ID, client ID, and client secret via credentials.
  • Uses HTTP requests with appropriate headers for authentication.
  • Pagination parameters are passed as query parameters.

Troubleshooting

  • No credentials returned!
    This error occurs if the required API authentication credentials are missing or not properly configured. Ensure that the API key credential is set up correctly in n8n.

  • Resource or Operation not found
    If the specified resource or operation does not exist, verify that the correct resource ("Integrator Schedule") and operation ("List Of Integrator Schedule") are selected.

  • API request errors
    Network issues, invalid parameters, or authentication failures may cause errors during the API call. Check the credentials, network connectivity, and parameter values.

  • Pagination parameters missing or invalid
    Providing invalid or missing pagination parameters might result in unexpected API responses or errors. Confirm that "Page No", "Page Size", and "Pageinate" are set appropriately.

Links and References

Discussion