• Overview
  • Configuration

Related-apps

Humanforce

Simplify workforce management by syncing Humanforce data with IT accounts.

AD & HR syncHCM

Overview

Humanforce is a workforce management platform designed for industries with shift-based and mobile workforces. Integrating Humanforce with Active Directory (AD) using ADManager Plus enables seamless synchronization of employee lifecycle events between HR and IT. When employees are added, updated, or offboarded in Humanforce, the corresponding changes are automatically reflected in AD—ensuring timely access provisioning, accurate permissions, and secure account deactivation.

 

Automated onboarding

Create AD accounts for new employees added in Humanforce, ensuring they have immediate access to internal systems.

 

Live role updates

Reflect department, location, or role changes from Humanforce in AD to maintain correct access across applications.

 

Secure offboarding

Disable or delete AD accounts when employees are removed in Humanforce, reducing security risks and maintaining compliance.

 

How to configure Humanforce integration in ADManager Plus

Prerequisites:

  • Humanforce uses basic authentication credentials to authorize API request
  • Authentication credentials: Use apiKey as the username and apiSecret as the password.

Privileges:

  • To import users (inbound action): Ensure the account used for authorization has permission to read all user accounts.
  • To perform any action or query in Humanforce (outbound action): Ensure the account used for authorization has permission to perform the desired action.
Note: ADManager Plus comes with a pre-configured set of APIs that helps perform basic actions with the integration. If the action you require is not available, please gather the necessary API details from Humanforce's API documentation to configure under inbound or outbound webhooks to perform the required actions.

Authorization configuration

  • Log in to ADManager Plus and navigate to Directory/Application Settings.
  • Go to Application Integrations, then search and select Humanforce.
  • Toggle the Enable Humanforce Integration button on.
  • In the Humanforce Configuration page, click Authorization.
  • Enter the authentication credentials. Enter apiKey as username and apiSecret value as password.
  • Click Configure.

Inbound webhook configuration

Inbound webhook enables you to fetch user data from Humanforce to ADManager Plus. The attribute mapping configured in this section can be selected as the data source during automation configuration to perform the desired action on the list of users received from the API response. To configure an inbound webhook for Humanforce:

  • Under Inbound Webhook, click Humanforce Endpoint Configuration.
  • In the Endpoint Configuration tab, an endpoint named "Humanforce - Get All Employees ENDPOINT;", comes pre-configured with an Endpoint URL, API Method, Headers, and Parameters fields to fetch user accounts from Humanforce. To use this pre-configured endpoint, replace {subdomain} with your Humanforce instance in the Endpoint URL field. If you would like to use a new endpoint to import users, you can configure one using the + Add API endpoint button and filling in the required fields as per Humanforce's API references. Click here to learn how. Note:
    • Authorization Header is preconfigured as a header for authenticating API requests as configured during Authorization Configuration.
    • You can add macros to your endpoint configuration to dynamically change it as per your requirement using the macro chooser component.
    • Refer to Humanforce's API references and configure additional headers and parameters, if required.
  • Once done, click Test & Save. A response window will display all the requested parameters that can be fetched using the API call. Click Proceed. Note:
  • Click Data Source - LDAP Attribute Mapping to match endpoints and to map AD LDAP attributes with the respective attributes in Humanforce.[ADManager Plus also lets you customize attribute format from Humanforce]
  • Click + Add New Configuration and perform the following:
    • Enter the Configuration Name and Description and select the Automation Category from the drop-down menu.
    • In the Select Endpoint field, select the desired endpoint and a Primary Key that is unique to a user (e.g. employeeIdentifier).
      Note: When multiple endpoints are configured, this attribute must hold the same value in all the endpoints.
    • In the Attribute Mapping field, select the attribute from the LDAP Attribute Name drop-down menu and map it with the respective column in Humanforce.
    • If you would like to create a new custom format for this, click Mapping Attribute.
    • Click Save.
Note: The attribute mapping configured in this section can be selected as the data source during automation configuration to perform the desired action on the list of users received from the API response.

Outbound webhook configuration

Outbound webhook enables you to update the changes made in AD using ADManager Plus to Humanforce or fetch or forward required details from Humanforce and synchronize them with AD.

To configure an outbound webhook for Humanforce:

  • Under Outbound Webhook, click Humanforce Webhook Configuration.
  • Click + Add Webhook.
  • Enter a name and description for this webhook.
  • Decide on the action that has to be performed and refer to Humanforce's API references for the API details such as the URL, headers, parameters, and other requirements that will be needed.
  • Select the HTTP method that will enable you to perform the desired action on the endpoint from the drop-down menu.
  • Enter the endpoint URL.
  • Configure the Headers, Parameters, and Message Type in the appropriate format based on the API call that you would like to perform.
  • Click Test and Save.
  • A pop up window will then display a list of AD users and groups to test the configured API call. Select the desired user or group over which this API request has to be tested, then click OK. This will make a real-time call to the endpoint URL, and the selected objects will be modified as per the configuration.
  • The webhook response and request details will then be displayed. Verify them for the expected API behavior and click Save.
Note: The webhooks configured in this section can be included in Orchestration Templates, which can be used in event-driven and scheduled automations. They can also be applied directly to desired users to perform a sequence of actions on them (under Management > Advanced Management > Orchestration).