Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Webhook Repository → List Of Webhook

AI-generated

Overview

This node integrates with the Halo PSA API to perform various operations on different resources. Specifically, for the Webhook Repository resource and the List Of Webhook operation, it retrieves a list of webhooks from the Halo PSA system. This is useful for scenarios where you want to programmatically access and manage webhook configurations, such as monitoring active webhooks, auditing webhook setups, or integrating webhook data into other workflows.

Practical examples include:

  • Automatically fetching all configured webhooks to display or log them.
  • Filtering webhooks by type or whether they are related to Azure Automation.
  • Using the retrieved webhook list to trigger further automation or notifications in n8n.

Properties

Name Meaning
Isazureautomation A query parameter to filter webhooks based on whether they are related to Azure Automation. Possible values depend on the API but typically boolean or specific flags.
Type A query parameter to filter webhooks by their type. The exact types depend on the Halo PSA API's webhook classification.

These properties are sent as query parameters when requesting the list of webhooks, allowing users to narrow down the results returned by the API.

Output

The node outputs an array of JSON objects, each representing a webhook retrieved from the Halo PSA API. Each item in the output corresponds to one webhook and contains all its details as provided by the API response.

The json field includes webhook properties such as identifiers, configuration details, status, and any metadata returned by the API.

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 via custom headers.
  • No additional external services beyond the Halo PSA API are required.

Troubleshooting

  • No credentials returned!
    This error occurs if the node cannot retrieve the necessary API credentials. Ensure that the credentials are properly configured in n8n and linked to the node.

  • Resource or Operation not found
    If the specified resource or operation does not exist, verify that the correct resource ("Webhook Repository") and operation ("List Of Webhook") names are used.

  • API request errors
    Errors from the API (e.g., authentication failures, invalid query parameters) will be returned in the output JSON under an error property if "Continue On Fail" is enabled. Otherwise, the node execution will stop with an error message. Check the API credentials and query parameters for correctness.

  • Invalid query parameters
    Passing unsupported or incorrectly formatted values for Isazureautomation or Type may cause the API to reject the request. Consult the Halo PSA API documentation for valid values.

Links and References

If you need more detailed information about other operations or resources, feel free to ask!

Discussion