Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Azure AD Connection → Post Undefined

AI-generated

Overview

This node integrates with the Halo PSA API, specifically targeting the "Azure AD Connection" resource with a "Post Undefined" operation. It allows users to send complex JSON payloads to configure or update Azure Active Directory connection settings within Halo PSA. This is useful for automating synchronization and mapping configurations between Azure AD and Halo PSA entities such as users, agents, sites, roles, devices, clients, tickets, and more.

Typical use cases include:

  • Automating the import and mapping of Azure AD users and groups into Halo PSA.
  • Defining detailed mappings for user roles, agent roles, priorities, and other custom fields.
  • Managing integration scopes and license assignments programmatically.
  • Updating connection settings in bulk via structured JSON data.

Properties

Name Meaning
Body A JSON object representing the full configuration for the Azure AD connection. It includes multiple nested arrays and objects for mappings related to users, agents, roles, sites, devices, clients, tickets, licenses, and integration types. The structure supports detailed filters, criteria, and field mappings to customize how Azure AD data is imported and synchronized with Halo PSA.

The "Body" property expects a JSON input that can contain keys such as:

  • mappings_user
  • mappings_agent
  • mappings_agent_roles
  • mappings_site (with nested filters and site_mappings_user)
  • user_matching_list
  • agent_matching_list
  • mappings_cab
  • licensed_roles_list
  • mappings_device
  • mappings_client
  • mappings_ticket
  • halo_integrator_import_types
  • current_scopes
  • mappings_priority
  • mappings_user_roles
  • mappings_xtype (with nested field_mappings, tag_list_pairs, criteria)
  • named_roles_list
  • mappings_new_user
  • halointegrator_allowedclientidslist
  • user_licence
  • _deltareset

Each key typically holds an array of objects defining specific mapping or configuration details.

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output JSON contains the response from the Halo PSA API after posting the provided Azure AD connection configuration.

  • The json field contains the API response, which may include success confirmation, updated resource details, or error messages.
  • There is no binary data output for this operation.

Dependencies

  • Requires an active connection to the Halo PSA API.
  • Needs credentials including base URL, tenant identifier, client ID, and client secret for authentication.
  • The node uses HTTP POST requests with JSON bodies to communicate with the API.
  • No additional external services are required beyond the Halo PSA API.

Troubleshooting

  • No credentials returned!: Ensure that valid API credentials are configured in n8n for the Halo PSA service.
  • Resource or Operation not found: Verify that the resource name is exactly "Azure AD Connection" and the operation is correctly set to "Post Undefined".
  • Invalid JSON body: The "Body" property must be valid JSON. Use proper JSON formatting and ensure all required fields are included.
  • API errors: If the API returns errors, check the response message in the output JSON for details. Common issues might include invalid mappings, missing required fields, or permission problems.
  • Network or authentication failures: Confirm network connectivity and that the API credentials have sufficient permissions.

Links and References

Discussion