Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Webhook → 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 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 fetch and manage webhook configurations, monitor active webhooks, or synchronize webhook data with other systems.

Practical examples include:

  • Automatically fetching all configured webhooks to audit or display them in a dashboard.
  • Filtering webhooks by type or automation status to trigger specific workflows.
  • Integrating webhook management into broader IT service management processes.

Properties

Name Meaning
Isazureautomation Filter webhooks based on whether they are related to Azure Automation.
Type Filter webhooks by their type. The exact types depend on the Halo PSA API's webhook types.

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

Output

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

If the API supports binary data for webhooks (not indicated here), it would be included accordingly, but this operation primarily returns JSON data describing webhooks.

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 dependencies beyond the Halo PSA API and n8n's HTTP request capabilities.

Troubleshooting

  • No credentials returned!: Ensure that the API credentials are correctly configured and available in n8n.
  • Resource or Operation not found: Verify that the selected resource is "Webhook" and the operation is "List Of Webhook".
  • API request errors: Network issues, invalid credentials, or incorrect query parameters can cause failures. Check the error message returned in the output JSON for details.
  • If the node is set to continue on failure, errors will appear in the output JSON under an error key; otherwise, the node execution will stop.

Links and References

Discussion