• Overview
  • Configuration

Related-apps

GoCo

Streamline employee record management by connecting GoCo with directories.

AD & HR syncHCM

Overview

Integrating GoCo with Active Directory via ADManager Plus enables organizations to automate user provisioning and deprovisioning based on real-time HR events. As employee records are created, updated, or removed in GoCo, corresponding identity actions are triggered in Active Directory (AD), ensuring faster access delivery, consistent user data, and secure offboarding. This tight HR-IT sync helps reduce manual work, improve onboarding efficiency, and maintain access compliance.

 

Automated onboarding

Instantly create AD accounts when new hires are added in GoCo, with preconfigured roles and permissions.

 

Live access updates

Reflect role, department, or manager changes in AD to keep access aligned with evolving responsibilities.

 

Secure exits

Disable or delete AD accounts when employees are offboarded in GoCo to eliminate lingering access.

 

Prerequisites:

Please ensure to provide the bearer token to retrieve desired information and perform tasks in GoCo. Refer to GoCo API references for more details.

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 GoCo (outbound action): Ensure the account used for authorization has permission to perform the desired action.
Note: ADManager Plus comes with a preconfigured 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 the GoCo API documentation to configure the inbound/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 for and select GoCo.
  • Toggle the Enable GoCo Integration button on.
  • In the GoCo Configuration page, click Authorization.
  • Perform the steps to generate bearer token in GoCo and paste the bearer token in the Value field.
  • Replace the {companyUrlName} with the company URL name in all URLs.
  • Click Configure.

Inbound webhook configuration

Inbound webhook enables you to fetch user data from GoCo and transfer it to ADManager Plus. To configure an inbound webhook for GoCo:

  • Under Inbound Webhook, click GoCo Endpoint Configuration.
  • In the Endpoint Configuration tab, an endpoint, GoCo - List All Employees ENDPOINT, comes preconfigured with an Endpoint URL, API Method, Headers, and Parameters fields to fetch user accounts from GoCo. If you would like to use this preconfigured endpoint, replace {companyURLname} with the name of your GoCo instance in the Endpoint URL field. However, 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 GoCo's API references. Learn how. Note:
    • The 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 GoCo'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. After verifying if the requested parameters have been called to action, click Proceed. Note:
    • Refer to GoCo's API references for the parameters that must be configured to fetch only specific parameters.
    • You can configure multiple endpoints for GoCo using the + Add API endpoint button. Learn how.
  • Click Data Source - LDAP Attribute Mapping to match endpoints and to map AD LDAP attributes with the respective attributes in GoCo.
  • 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 (for example, id).
      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 attribute in GoCo.
    • If you would like to create a new custom format for this, click Add New Format.
    • Click Save.
  • Configure an automation with the required action, repeat frequency, and the above configured attribute mapping configuration.
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

An outbound webhook enables you to send changes made in AD using ADManager Plus to GoCo and carry out tasks in GoCo—all from ADManager Plus. To configure an outbound webhook for GoCo:

  • Under Outbound Webhook, click GoCo 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 GoCo's API references for the API details, such as the URL, headers, parameters, and other requirements.
  • 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 on which to test the configured API call. Select the desired user or group on which this API request has to be tested and click OK. This will make a real-time call to the endpoint URL, and the selected objects will be modified according to 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).