The Sprinklr Extensions Library is a centralized, searchable repository of pre-built external API integrations. These integrations, called templatized extensions, provide ready-to-use connectors for widely used platforms such as Salesforce, Zendesk, and ServiceNow, etc.

By using the Extensions Library, you can integrate external systems into Sprinklr workflows and AI Agents with minimal setup effort. This approach reduces development overhead, ensures consistent API usage, and improves time-to-value.

The Extensions Library is designed to:

• Reduce manual effort in API integration.

• Accelerate workflow and AI Agent configuration.

• Provide consistent, version-controlled API setups.

• Offer secure authentication, versioning, monitoring, and fallback options.

Key Features

The library includes several features designed to simplify configuration, improve maintainability, and provide reliable integration with external platforms.

Pre-Built Templates: Pre-built templates let you configure APIs without needing to start from scratch. They provide tested, ready-to-use options for major platforms.

​

Authentication Binding: Authentication binding ensures secure and flexible credential management when connecting to multiple instances of the same platform.

​

Versioning Support: Versioning support ensures that existing workflows remain unaffected while giving you access to updated API templates.

Monitoring and Alerts: The library includes built-in monitoring to help you track extension health and prevent disruptions to workflows.

• Health monitoring of all configured extension instances.

• Alerts for issues such as:

• API call failures.

• Credential expiration.

• Deprecation notices.

• An Admin Dashboard provides visibility into extension health, usage, and alerts.

​

Manual Configuration Fallback: If the library does not have a template for your use case, you can configure the API manually while keeping the same management capabilities.

• If a template is unavailable, users can configure APIs manually.

• Provides seamless fallback between library-based configuration and manual setup.

Prerequisites

Before you begin, make sure your user account has the following External API permissions:

• View: Allows you to access and view existing external API configurations.

• Create: Allows you to add new external API configurations.

• Edit: Allows you to modify existing external API configurations.

• Delete: Allows you to remove external API configurations.

Configure External APIs Using Templates

You can configure External APIs quickly by selecting pre-built templates from the Extensions Library. The process includes selecting a template, entering connection details, and finalizing the configuration.

Step 1: Access the Extensions Library

The steps to access the Extensions Library depend on whether your environment uses the old All Settings UI or the new All Settings UI.

Access Extension Library in Old All Settings UI

Follow the steps below to access Extensions Library in Old All Settings UI:

• Navigate to All Settings from Sprinklr Launchpad.

• In the Platform Settings window, select Manage Customer from left toolbar.

• From the list of options, choose External API. You can also use the search bar at the top to quicky find it.

• The External API Record Manager opens.

Access Extension Library in New All Settings UI

Follow the steps below to access Extensions Library in new All Settings UI:

• Navigate to All Settings from Sprinklr Launchpad.

• Select APIs and Integrations from left navigation bar to open detailed record manager.

• Click the External API option from left menu to access External API Record Manager.

Step 2: Add an External API

• In the External API Record Manager, click Add External API button in the top-right corner.

  • The Templates Library opens.

• Select the template that best matches your integration requirements.

  • For example, choose Salesforce if you want to integrate with Salesforce APIs.

• On the selected platform card, review the available API details, such as:

  • Method type (GET, POST, etc.)

  • Endpoint

  • Version

• After verifying the details, click Next to continue with the configuration.

Step 3: Configure the API

Once you have chosen a template, provide the required configuration details. Use the External API Configuration page to customize the template. You can quickly locate API endpoints using the Search bar in the endpoint list on the right side of the OpenAPI specification form.

Complete the following fields to configure the selected API template.

• Connection: Select the connection credentials from the dropdown. The list is pre-populated with credentials stored in Sprinklr.

• API Name: Provide a unique, descriptive name for the API configuration.

• Select API Endpoint: Select the endpoint from the dropdown.

• Endpoint URL: The system auto-fills the Endpoint URL with the configured value.

• Description: Enter a description to document the purpose of this configuration.

Use the '+ External API' button to add multiple API endpoints in the same configuration.

Step 4: Save the Configuration

Click the Save button at the bottom-right corner to apply your configuration settings.

• The system validates the API after you save the configuration. You will get a Configuration Summary screen once the validation is complete.

• If the validation is successful, the API is added and becomes available in the External API Record Manager.

Filters in Extensions Manager

You can use filters in Extensions Manager to quickly find and manage extensions based on key attributes. Filters appear at the top of the Extensions Manager page and work together to narrow the results.

• Credentials Filter

Use the Credentials filter to view extensions linked to specific credentials.

What you can do: 

• Search for credentials by name.

• Select one or more credentials.

• Add or remove selections using the plus and minus controls.

• Clear All selections in one action.

Behavior:

The list shows all credentials available in the environment.  The result set updates only after you select Apply Filters. Extensions without the selected credentials are excluded from the view.

• Created By Filter

Use the Created By filter to view extensions created by specific users.

What you can do:

• Search for users by name.

• Select one or more creators.

• Combine this filter with others for precise results.

Behavior: Only extensions created by the selected users appear. This filter helps with ownership tracking and audits.

• Application Name Filter

Use the Application Name filter to view extensions by the application they integrate with.

What you can do: 

• Search for an application.

• Select one or more application names such as Wrike, Zendesk, Zoom, or Custom API. 

• Apply the filter to refine the list.

Behavior: 

The list includes both built-in and custom applications. Extensions that match any selected application appear in the results.

• Platform Type Filter

Use the Platform Type filter to group extensions by platform category.

What you can do: 

• Search for a platform type. 

• Select one or more categories such as CI/CD, Project Management, Collaboration, or Data Visualization.

• Apply the filter to update the view.

Behavior: 

Platform Type reflects the primary use case of the application.

Selecting multiple platform types returns extensions that match any selected category.

Applying and Clearing Filters

• Filters do not take effect until you select Apply Filters.

• Select Cancel to close the filter panel without applying changes.

• Use Clear All to reset selections within a filter.

• You can apply multiple filters at the same time to narrow results further.

Result Behavior

• Filters work together using an AND condition across filter types.

• Within a single filter, multiple selections use an OR condition. 

• The filtered list updates immediately after filters are applied.
  

The Sprinklr Extensions Library streamlines the process of connecting external platforms with Sprinklr workflows. By using pre-built, version-controlled templates with secure authentication, monitoring, and fallback mechanisms, teams can configure and maintain API integrations efficiently with minimal risk of misconfiguration.