Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Webhook Repository → Get One Webhook

AI-generated

Overview

This node interacts with the Halo PSA API to perform various operations on different resources. Specifically, for the Webhook Repository resource and the Get One Webhook operation, it retrieves detailed information about a single webhook by its unique identifier.

Typical use cases include:

  • Fetching configuration or status details of a specific webhook in your Halo PSA system.
  • Integrating webhook data retrieval into automated workflows, such as monitoring or auditing webhook setups.
  • Using the retrieved webhook details to trigger further actions or conditional logic within n8n.

Properties

Name Meaning
Id The unique identifier of the webhook to retrieve. This is a required string input.
Includedetails Optional query parameter to specify whether to include additional details in the response.

Output

The node outputs JSON data representing the webhook object retrieved from the Halo PSA API. The structure corresponds to the webhook's properties as defined by the API, including but not limited to its ID, URL, events subscribed to, status, and any other metadata.

No binary data output is produced by this operation.

Example output snippet (conceptual):

{
  "id": "12345",
  "url": "https://example.com/webhook",
  "events": ["ticket.created", "ticket.updated"],
  "active": true,
  "description": "Support ticket webhook"
}

Dependencies

  • Requires an API key credential for authenticating with the Halo PSA API.
  • The node expects the base URL, tenant identifier, client ID, and client secret to be provided via credentials.
  • Network access to the Halo PSA API endpoint is necessary.

Troubleshooting

  • Missing Credentials Error: If no credentials are returned, ensure that the API authentication token and related settings are correctly configured in n8n.
  • Resource or Operation Not Found: Errors indicating missing resource or operation suggest misconfiguration of the node parameters; verify that "Webhook Repository" and "Get One Webhook" are selected properly.
  • Invalid Id Parameter: Providing an empty or incorrect webhook ID will cause the API call to fail; confirm the ID is valid and exists in the Halo PSA system.
  • API Request Failures: Network issues, invalid credentials, or insufficient permissions can cause request errors. Check connectivity and credential validity.
  • JSON Parsing Issues: If additional query parameters or JSON bodies are malformed, the node may throw parsing errors. Ensure all JSON inputs are well-formed.

Links and References

Discussion