Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Dashboard Links → Post Undefined

AI-generated

Overview

This node integrates with the Halo PSA API, allowing users to perform various operations on different resources within the Halo PSA system. Specifically, for the Dashboard Links resource and the Post Undefined operation, it sends a POST request with a complex JSON body payload to create or update dashboard link configurations.

Typical use cases include automating the management of dashboard widgets, access controls, filters, user access settings, and other related dashboard elements in Halo PSA. For example, an IT service manager could automate the setup of customized dashboards for different teams by posting structured widget and access control data.

Properties

Name Meaning
Body A JSON object representing the full configuration of dashboard links, including widgets, actions, series, colours, translations, access control, filters, and user access. This property expects a detailed JSON structure describing all aspects of the dashboard setup.

The "Body" property accepts a JSON input that defines nested structures such as widgets with their actions, fields, users, attachments, roles, external links, and many other sub-entities. The user must provide this JSON either directly or via expression parsing.

Output

The node outputs an array of items where each item contains a json field holding the response from the Halo PSA API after the POST request. The response typically includes the created or updated dashboard link data as returned by the API.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Halo PSA API.
  • Needs the base URL, tenant identifier, client ID, and client secret configured in the credentials.
  • Uses HTTP POST requests with JSON bodies to communicate with the Halo PSA REST API.

Troubleshooting

  • No credentials returned!: This error occurs if the node cannot retrieve the required API authentication credentials. Ensure that the API key credential is properly set up and connected to the node.
  • Resource or Operation not found: If the specified resource or operation does not exist in the node's configuration, verify that the correct resource ("Dashboard Links") and operation ("Post Undefined") are selected.
  • Invalid JSON in Body: Since the Body property requires valid JSON, malformed JSON will cause errors. Use JSON validators or n8n's expression editor to ensure correctness.
  • API request failures: Network issues, incorrect credentials, or invalid request payloads can cause the API call to fail. Check the error message returned in the output for details and verify connectivity and payload structure.

Links and References

Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.

Discussion