Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Azure AD Mapping → List Of Azure AD Mapping

AI-generated

Overview

This node integrates with the Halo PSA API to perform various operations on different resources. Specifically, for the Azure AD Mapping resource with the List Of Azure AD Mapping operation, it retrieves a list of Azure Active Directory mappings associated with a given connection ID.

Typical use cases include synchronizing or auditing Azure AD mappings within an IT service management workflow, automating user provisioning, or integrating Azure AD data into other systems via n8n workflows.

For example, you might use this node to fetch all Azure AD mappings linked to a specific connection and then process or analyze them downstream in your automation.

Properties

Name Meaning
Connection Id The identifier of the Azure AD connection for which to list the mappings.

Output

The node outputs an array of JSON objects, each representing an Azure AD mapping retrieved from the API. Each item corresponds to one mapping entry returned by the "List Of Azure AD Mapping" operation.

The output structure is:

[
  {
    "json": {
      // Azure AD mapping details as returned by the API
    },
    "pairedItem": {
      "item": <index_of_input_item>
    }
  }
]

No binary data output is produced by this operation.

Dependencies

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

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

  • The node uses these credentials to authenticate API requests via custom headers.

  • No additional external dependencies are required beyond the configured API credentials.

Troubleshooting

  • No credentials returned!
    This error indicates that the node could not retrieve the necessary API credentials. Ensure that the Halo PSA API credentials are properly configured in n8n.

  • Resource or Operation not found
    If the specified resource or operation does not exist, verify that the correct resource ("Azure AD Mapping") and operation ("List Of Azure AD Mapping") names are used.

  • API request errors
    Network issues, invalid credentials, or incorrect connection IDs may cause API request failures. Check the error message returned in the node output for details.

  • JSON parsing errors
    If additional parameters are provided as JSON strings, ensure they are correctly formatted.

  • To continue processing subsequent items even if one fails, enable the "Continue On Fail" option in the node settings.

Links and References

Discussion