Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Faults → Post Undefined

AI-generated

Overview

This node integrates with the Halo PSA API to create or post fault records. Specifically, for the "Faults" resource and the "Post Undefined" operation, it sends a detailed JSON body representing a fault ticket or issue to the Halo PSA system. This is useful in scenarios where you want to automate the creation of fault tickets or issues within Halo PSA from workflows, such as logging incidents detected by monitoring tools, creating support tickets from form submissions, or syncing fault data from other systems.

Practical examples:

  • Automatically create a fault ticket in Halo PSA when an error alert is received.
  • Post detailed fault information including custom fields, attachments, and related entities from an external system into Halo PSA.
  • Integrate with other ITSM or monitoring platforms to keep fault records synchronized.

Properties

Name Meaning
Body A JSON object containing the full details of the fault to be created. This includes nested structures such as child ticket IDs, start and target dates with timezones, custom fields, time entries, addresses, approvers, attachments, qualifications, assets, todo lists, budgets, audit logs, tags, external links, milestones, AI suggestions, related tickets, workflow history, Freshdesk ticket data, agent booking info, outcomes, schedules, user linked sites, and many other complex nested properties. The JSON structure supports extensive customization and detailed fault record representation.

Note: The "Body" property expects a JSON input that can include a very comprehensive set of nested fields to fully describe the fault and its related data.

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output item contains the response from the Halo PSA API after posting the fault data. The response JSON typically includes confirmation of the created fault record, any generated IDs, status messages, or error details if the request failed.

If the node encounters errors during execution and "Continue On Fail" is enabled, the output will contain an error message in the JSON field for the respective item.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Halo PSA API.
  • Needs configuration of base URL, tenant ID, client ID, and client secret for the Halo PSA instance.
  • Uses HTTP requests with appropriate headers for authentication and content type.
  • Relies on n8n's built-in HTTP request helper methods.

Troubleshooting

  • Common Issues:

    • Missing or invalid credentials will cause authentication failures.
    • Incorrectly formatted JSON in the "Body" property may lead to API errors.
    • Network connectivity issues to the Halo PSA API endpoint.
    • Using unsupported or incorrect resource-operation combinations.

  • Error Messages:

    • "No credentials returned!": Ensure the API key credential is configured correctly.
    • "Resource Faults not found" or "Operation Post Undefined not found for resource Faults": Verify the resource and operation names are correct.
    • API error responses with validation messages: Check the JSON body structure and required fields according to Halo PSA API documentation.

  • Resolution Tips:

    • Validate JSON input before running the node.
    • Confirm all required authentication parameters are set.
    • Enable "Continue On Fail" to handle partial failures gracefully.
    • Review Halo PSA API documentation for required fields and formats.

Links and References

Note: The provided JSON example for the "Body" property is highly complex and deeply nested, reflecting the rich data model supported by Halo PSA for faults. Users should tailor the JSON payload to their specific use case and ensure compliance with the Halo PSA API schema.

Discussion