Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Microsoft Subscription Mapping → Post Undefined

AI-generated

Overview

This node integrates with the Halo PSA API to perform operations related to Microsoft Subscription Mapping. Specifically, for the "Post Undefined" operation under the "Microsoft Subscription Mapping" resource, it sends a JSON payload representing complex mapping configurations to the API endpoint.

Typical use cases include automating the synchronization or configuration of user, agent, site, device, ticket, and role mappings between Microsoft subscriptions and Halo PSA systems. This can be useful in IT service management workflows where subscription data needs to be programmatically updated or maintained.

For example, an organization might use this node to post detailed mapping configurations that define how users and agents correspond to Azure connections, sites, roles, and licenses within their Halo PSA environment.

Properties

Name Meaning
Body A JSON object containing detailed mapping configurations for Microsoft Subscription Mapping. It includes nested structures such as azure_connection (with user, agent, roles, site mappings, etc.), mappings_folder, sharepoint_list, and sharepoint_site. The body defines how various entities like users, agents, devices, tickets, and roles are mapped and filtered.

The "Body" property expects a JSON input structured according to the complex schema shown in the default value, allowing extensive customization of the mapping data sent to the API.

Output

The node outputs the JSON response returned by the Halo PSA API after posting the mapping data. The output is structured as:

{
  "json": { /* API response object */ },
  "pairedItem": { "item": <index> }
}
  • json: Contains the full response from the API, which may include success confirmation, error messages, or details about the processed mappings.
  • pairedItem: Links the output to the corresponding input item index.

No binary data output is indicated for this operation.

Dependencies

  • Requires valid credentials for the Halo PSA API, including base URL, tenant identifier, client ID, and client secret.
  • The node depends on network connectivity to the Halo PSA API endpoint.
  • No additional external services beyond the Halo PSA API are required.

Troubleshooting

  • Missing Credentials: If no credentials are provided or they are invalid, the node will throw an error "No credentials returned!" Ensure that the API authentication details are correctly configured.
  • Resource or Operation Not Found: Errors like "Resource Microsoft Subscription Mapping not found" or "Operation Post Undefined not found for resource Microsoft Subscription Mapping" indicate misconfiguration of the resource or operation parameters.
  • Invalid JSON Body: Since the body is parsed from JSON, malformed JSON input will cause parsing errors. Validate the JSON structure before execution.
  • API Request Failures: Network issues, incorrect API endpoint URLs, or authorization failures will result in request errors. Check API credentials, endpoint accessibility, and permissions.
  • Continue On Fail: If enabled, the node will continue processing subsequent items even if some fail, returning error details in the output JSON.

Links and References

Note: The node's execute method dynamically constructs the API request based on the resource and operation parameters, sending the provided JSON body to the configured Halo PSA API endpoint with appropriate headers for authentication.

Discussion