Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Event Rule → 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 Event Rule resource and the Post Undefined operation, it sends a POST request with a JSON body to create or update event rules based on custom criteria, mappings, and value mappings.

Typical use cases include automating the creation or modification of event rules in Halo PSA as part of a workflow, such as dynamically adjusting alerting or monitoring rules based on external triggers or data processed earlier in the workflow.

For example, you might use this node to programmatically define how certain events are handled by specifying criteria and mappings without manually configuring them in the Halo PSA interface.

Properties

Name Meaning
Body A JSON object representing the event rule details to be sent in the request body. It includes arrays for values (with value_mappings), criteria, and mappings. This property allows full customization of the event rule's configuration. The default structure is:
json { "values": [ { "value_mappings": [ {} ] } ], "criteria": [ {} ], "mappings": [ {} ] }

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output item contains:

  • json: The parsed JSON response from the Halo PSA API after performing the POST request for the event rule.
  • If an error occurs and "Continue On Fail" is enabled, the output will contain an error field with the error message instead.

No binary data output is produced by this node.

Dependencies

  • Requires valid credentials for the Halo PSA API, including:

    • Base URL of the Halo PSA instance
    • Tenant identifier
    • Client ID
    • Client Secret

  • These credentials must be configured in n8n prior to using the node.

  • The node uses HTTP requests with appropriate headers (X-Tenant, X-HaloPSA-ClientId, X-HaloPSA-ClientSecret) to authenticate and interact with the API.

Troubleshooting

  • Common issues:

    • Missing or invalid credentials will cause the node to throw an error indicating no credentials were returned.
    • Incorrectly formatted JSON in the "Body" property can lead to parsing errors or API rejections.
    • Network connectivity problems or incorrect base URL may result in request failures.

  • Error messages:

    • "No credentials returned!": Ensure that the API credentials are properly set up in n8n.
    • "Resource Event Rule not found" or "Operation Post Undefined not found for resource Event Rule": Indicates a mismatch between selected resource/operation and the node's supported options.
    • API error responses will be passed through in the output if "Continue On Fail" is enabled; otherwise, they will stop execution.

  • Resolution tips:

    • Validate the JSON structure in the "Body" property before running the node.
    • Confirm that all required credential fields are correctly filled.
    • Check network access to the Halo PSA API endpoint.

Links and References

Discussion