• Overview
  • Configuration

Related-apps

Spryng

Sync messaging users in Spryng with directory data to centralize control.

Identity provisioningCollaboration & communication

Overview

Spryng is a cloud-based communication platform that enables businesses to send SMS, voice, and other notifications for alerts, authentication, and customer engagement. By integrating Spryng with ADManager Plus, you can automate the flow of identity data between your AD environment and Spryng. This ensures that user records are always up to date across systems and that communication workflows are triggered based on real-time changes in your directory.

 

Automate Spryng user provisioning using AD or HR data

Automatically pull user records from Spryng and create corresponding accounts in Active Directory, or vice versa. This eliminates manual entry, reduces errors, and ensures faster onboarding across systems.

 

Keep communication attributes in sync across AD and Spryng

Update phone numbers, usernames, or role-based access in one system and reflect the changes in the other using outbound webhooks. This ensures message delivery and permissions always align with user status in AD.

 

Trigger communication actions in Spryng based on AD events

Use ADManager Plus automations to trigger predefined Spryng actions to help streamline workflows for IT, HR, or security alerts.

 

Prerequisites:

Provide the Bearer Token to retrieve desired information and perform tasks in. Refer to the 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 Spryng (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 Spryng API documentation to configure under 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 and select Spryng.
  • Toggle the Enable Spryng Integration button on.
  • In the Configuration page, click Authorization.
  • Perform the steps to generate Bearer Token in and paste the Bearer Token in the Value field.
  • Click Configure.

Inbound webhook configuration

Inbound webhook enables you to fetch user data from and transfer 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 :

  • Under Inbound Webhook, click Endpoint Configuration.
  • In the Endpoint Configuration tab, an endpoint, LIST SUBACCOUNTS ENDPOINT, comes preconfigured with an Endpoint URL, API Method, Headers, and Parameters fields to fetch user accounts from Spryng. 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 Spryng'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 Spryng'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 Spryng's API references to know the Parameters that must be configured to fetch only specific parameters.
    • You can configure multiple endpoints for Spryng 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 Spryng.
  • 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, 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 Spryng.
    • If you would like to create a new custom format for this, click Add New Format.
    • 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

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

  • Under Outbound Webhook, click Spryng 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 Spryng'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).