Qualitor SOAP API

Consume Qualitor SOAP Webservices
Join our community

Overview

This node integrates with the Qualitor SOAP API, allowing users to call various web services provided by Qualitor. It supports multiple service categories such as General, Ticket, and Service webservices. The node constructs SOAP requests dynamically based on user input fields and sends them to the Qualitor API endpoint. Users can choose to receive the response either parsed as JSON or as raw XML.

Common scenarios include:

  • Automating ticket management by querying or updating tickets.
  • Accessing general or service-specific data from Qualitor systems.
  • Integrating Qualitor SOAP operations into broader workflows for IT service management.

For example, a user might query ticket details by specifying the "Ticket" service, an operation like "getTicket", and providing relevant field values such as ticket ID.

Properties

Name Meaning
Service Selects the Qualitor webservice category to use. Options: General, Ticket, Service
Parse Response? Whether to parse the SOAP XML response into JSON (true) or return raw XML (false)
Fields A collection of key-value pairs representing XML elements to include in the request payload

Output

The node outputs an array of items where each item contains a json property with a single field:

  • data: Contains the response from the Qualitor API.
    • If "Parse Response?" is enabled, this will be a JSON object parsed from the SOAP XML response.
    • Otherwise, it will be the raw XML string returned by the API.

No binary data output is produced by this node.

Dependencies

  • Requires an API authentication credential containing base URL, company ID, username, and password for the Qualitor SOAP API.
  • Uses the qs library to serialize parameters into query strings.
  • Uses the xml2js library to parse XML responses into JSON when requested.
  • The node makes HTTP POST requests to the Qualitor stateless webservice endpoint.

Troubleshooting

  • Invalid credentials or missing API keys: Ensure that the required API authentication details (base URL, company ID, username, password) are correctly configured.
  • Malformed XML or incorrect field names: The fields must correspond exactly to expected XML element names for the selected operation; otherwise, the API may return errors or empty results.
  • Parsing errors: If "Parse Response?" is enabled but the response is not valid XML or does not match expected structure, parsing may fail. In such cases, try disabling parsing to inspect raw XML.
  • Network or endpoint issues: Verify connectivity to the Qualitor API endpoint and that the URL is correct.

Links and References

Discussion