Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Power Shell Script → List Of Power Shell Script

AI-generated

Overview

This node integrates with the Halo PSA API to perform various operations on different resources. Specifically, for the "Power Shell Script" resource and its "List Of Power Shell Script" operation, it retrieves a list of PowerShell scripts from the Halo PSA system. This is useful in scenarios where you want to automate the retrieval and processing of PowerShell scripts managed within Halo PSA, such as auditing available scripts, integrating script data into workflows, or triggering further automation based on script metadata.

Practical examples include:

  • Automatically fetching all PowerShell scripts to display or log them.
  • Using the list to trigger execution or modification workflows.
  • Filtering scripts by type or client override parameters to tailor automation.

Properties

Name Meaning
Clientidoverride A string query parameter to override the client ID when listing PowerShell scripts.
Type A string query parameter to filter the list of PowerShell scripts by their type.

These properties are sent as query parameters in the API request to customize the returned list.

Output

The node outputs an array of JSON objects, each representing a PowerShell script retrieved from the Halo PSA API. The exact structure depends on the API response but typically includes script metadata such as IDs, names, types, and other relevant details.

If the node encounters errors during execution, it outputs JSON objects containing an error field with the error message.

No binary data output is involved in this operation.

Dependencies

  • Requires valid credentials for the Halo PSA API, including base URL, tenant identifier, client ID, and client secret.
  • The node uses these credentials to authenticate API requests.
  • No additional external dependencies beyond the Halo PSA API and n8n's HTTP request capabilities.

Troubleshooting

  • No credentials returned!: Indicates missing or invalid API credentials. Ensure that the required API authentication token and related credentials are correctly configured in n8n.
  • Resource or Operation not found: Happens if the specified resource or operation name does not match those supported by the node. Verify spelling and case sensitivity.
  • API request errors: Network issues, incorrect query parameters, or API permission problems can cause failures. Check the error messages returned in the output JSON for clues.
  • If the node is set to continue on failure, errors will be included in the output JSON; otherwise, they will stop execution.

Links and References


Note: The above summary is based solely on static analysis of the provided source code and property definitions.

Discussion