Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Uname Notification → List Of Uname Notification

AI-generated

Overview

This node integrates with the Halo PSA API to list notifications related to "Uname Notification". It allows users to retrieve a filtered list of notifications based on various query parameters such as agent ID, role ID, notification type, and webhook ID. This is useful in scenarios where you want to monitor or process notifications generated by agents or roles within the Halo PSA system.

Practical examples include:

  • Fetching all notifications for a specific agent to track their activity.
  • Filtering notifications by role to audit role-specific alerts.
  • Retrieving notifications of a certain type to trigger downstream workflows.

Properties

Name Meaning
Agent Id Filter notifications by a specific agent's identifier.
Restrictto Agent Id Further restrict notifications to a particular agent ID.
Role Id Filter notifications by a specific role identifier (string).
Showall Option to show all notifications without filtering.
Type Filter notifications by their type.
Webhook Id Filter notifications associated with a specific webhook identifier (string).

Output

The node outputs an array of JSON objects representing the notifications retrieved from the Halo PSA API. Each item corresponds to one notification and contains all relevant data fields returned by the API for that notification.

If the API supports binary data in responses (not indicated here), it would be included accordingly, but this operation appears to only return JSON data.

Dependencies

  • Requires an API key credential for authenticating with the Halo PSA API.
  • The node expects configuration of base URL, tenant, client ID, and client secret via credentials.
  • No additional external dependencies beyond the Halo PSA API and n8n core modules.

Troubleshooting

  • No credentials returned!: Ensure that the API key credential is properly configured and connected in n8n.
  • Resource or Operation not found: Verify that the resource is set to "Uname Notification" and the operation to "List Of Uname Notification".
  • API request errors: Check network connectivity and validity of query parameters. Invalid or missing parameters may cause the API to reject requests.
  • If the node returns an error object in the output JSON, inspect the error message for details.
  • Use the "Continue On Fail" option to handle errors gracefully in batch executions.

Links and References

Discussion