• Overview
  • Configuration

Related-apps

Pipedrive

Simplify IT workflows with Pipedrive-ADManager Plus integration

Identity provisioning

Pipedrive is a CRM platform that centralizes sales, marketing and customer management processes, providing an all-in-one solution to boost sales efficiency and drive business growth. Integrating ADManager Plus with Pipedrive enables organizations to automate user lifecycle management, reducing the manual workload for IT teams. By synchronizing user data between Pipedrive and Active Directory, the integration automates user provisioning, updates, and de-provisioning across AD, Exchange, Microsoft 365, and other integrated applications, ensuring seamless and efficient user management.

 

Automate user provisioning

Automating the creation, updating, and deletion of user accounts in AD and other business applications based on changes in Pipedrive reduces manual workload for IT teams and improves the accuracy of user management processes.

 

Bi-directional sync

With synchronized user data between Pipedrive and AD, organizations ensure that user access and permissions are consistently updated across all platforms, ensuring that business operations are fully aligned with the latest user roles and organizational changes.

 

Pipedrive uses OAuth 2.0 to authorize API requests.

It requires a client_id and client_secret for authorization.

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 Pipedrive (outbound action): Ensure the account used for authorization has permission to perform the desired action.

Note: ADManager Plus comes with preconfigured set of APIs that help perform basic actions with the integration. If the action you require is not available, please gather the necessary API details from Pipedrive's API documentation to configure inbound or outbound webhooks to perform the required actions.

Authorization configuration

  • Log in to ADManager Plus and navigate to the Automation tab.
  • In the left pane, under Configuration, click Application Integrations.
  • Under Enterprise Applications, click Pipedrive.
  • Toggle the Enable Pipedrive Integration button on.
  • On the Pipedrive Configuration page, click Authorization.
  • Perform the steps to generate a client_id and client_secret from Pipedrive, and paste them in the respective value fields.
  • Click Configure.

Inbound webhook configuration

Inbound webhooks enable you to fetch user data from Pipedrive and send it to ADManager Plus. The attribute mapping configured in this section can be selected as the data source during automation configuration. To configure an inbound webhook for Pipedrive:

  • Under Inbound Webhook, click Pipedrive Endpoint Configuration.

  • In the Endpoint Configuration tab, an endpoint, Pipedrive USERS ENDPOINT, comes preconfigured. 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 Pipedrive's API documentation. Click here to learn how.

    Note:

    • The API key value pair is preconfigured as a header for authenticating API requests as configured during authorization configuration.
    • Macros: You can add macros to your endpoint configuration to dynamically change it as per your requirement using the macro chooser component
    • Refer to Pipedrive's API documentation and configure additional headers and parameters, if required. In the Settings tab, the Repeat calling this endpoint option will be configured to fetch 30 records per call. This will be repeated until no next page token is received.

  • 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 Pipedrive's API documentation to learn about the parameters that must be configured to fetch only specific parameters.
    • You can configure multiple endpoints for Pipedrive using the + Add API endpoint button. Click here to learn how.
  • Click Data Source - LDAP Attribute Mapping to match endpoints and to map AD LDAP attributes with the respective attributes in Pipedrive.

  • Click + Add New Configuration and perform the following actions:

    • 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 attribute in Pipedrive.
    • If you would like to create a new custom format for this, click Add New Format.

Outbound webhook configuration

Outbound webhooks enable you to send changes made in AD to Pipedrive, fetch data from Pipedrive, and carry out tasks in Pipedrive—all from ADManager Plus. The webhooks configured in this section can be included in Orchestration Templates, which in turn can be used during event-driven and scheduled automations. They can also be applied directly on desired users to perform a sequence of actions on them (Management > Advanced Management > Orchestration). To configure outbound webhooks for Pipedrive:

  • Under Outbound Webhook, click Pipedrive 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 Pipedrive's API documentation for the API details, such as URL, headers, and parameters.
  • 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 and 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.