Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Analyzer Profile → Post Undefined

AI-generated

Overview

This node integrates with the Halo PSA API to perform various operations on different resources. Specifically, for the "Analyzer Profile" resource and the "Post Undefined" operation, it sends a POST request with a complex JSON body payload to create or update an analyzer profile or related data in the Halo PSA system.

Typical use cases include automating the creation or updating of detailed analyzer profiles within Halo PSA, which may contain extensive nested configuration data such as columns, filters, schedules, reports, permissions, and other metadata. This is useful for organizations that want to programmatically manage their analysis profiles as part of IT service management workflows.

For example, you might use this node to:

  • Create a new analyzer profile with specific reporting columns and filters.
  • Update scheduling rules and permissions for an existing profile.
  • Automate bulk updates of profile configurations based on external data sources.

Properties

Name Meaning
Body A JSON object representing the full analyzer profile data to be sent in the POST request. This includes nested structures such as available columns, filters, conditions, schedules, reports, permissions, and many other detailed configuration fields. The property expects a valid JSON structure matching the Halo PSA API schema for analyzer profiles.

Output

The node outputs the JSON response from the Halo PSA API after performing the POST request. The output contains the server's response data, which typically includes confirmation of the created or updated analyzer profile, any generated IDs, status messages, or error details if the request failed.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Halo PSA API.
  • Requires credentials including base URL, tenant identifier, client ID, and client secret for authentication.
  • The node uses HTTP requests with appropriate headers for authentication.
  • No additional external dependencies beyond the configured Halo PSA API credentials.

Troubleshooting

  • No credentials returned!: Ensure that the API credentials are properly configured in n8n and linked to the node.
  • Resource or Operation not found: Verify that the resource name is exactly "Analyzer Profile" and the operation is correctly set to "Post Undefined".
  • Invalid JSON in Body: The Body property must contain valid JSON. Use the built-in JSON editor or validate your JSON before running.
  • API errors: If the Halo PSA API returns errors (e.g., 400 Bad Request), check the structure and required fields of the JSON body against the Halo PSA API documentation.
  • Network issues: Confirm network connectivity to the Halo PSA API endpoint and that firewall or proxy settings allow outbound requests.
  • Continue On Fail: If enabled, the node will return error messages in the output JSON instead of stopping execution.

Links and References

Discussion