In Sprinklr, connectors can be classified based on how they are executed and how data is ingested into the platform. This classification helps in understanding the operational behaviour of the connectors and their role in managing data flow effectively.

Different Types of Connectors

Connectors are classified on the basis of how data is ingested into the platform, and how the connectors are run.

1. Based on how data is ingested: Connectors can be classified based on how they ingest data from the source into Sprinklr. These can be: 

   • File Based Connectors: To run these connectors, users will need to provide file(s) in the form of an excel file, or zip file. These files can be uploaded locally while running the connector or they can be fetched from an external source like SFTP, S3, GCS, and Azure. 

   • Database Based Connectors: These connectors utilise a DBMS connection like SQL to fetch data from a database.

   • API based Connectors: The connectors utilise APIs exposed by any 3^rd party provider (like Zendesk, Freshdesk, Genesys) to create entities on Sprinklr.

2. Based on how the connectors run:  

   • Recurring Connectors: These connectors can create entities in the platform in a live pipeline like manner without any intervention form the user. These connectors need to be activated so that they can start fetching the cases in a live manner. Examples of these connectors would be SFTP, S3, GCS, Azure, SQL or API based connectors.

   • Non-Recurring Connectors: These connectors need to be run manually each time to create the respective entity in the platform. Example of these connectors can be File based connector.  
     

     Note: Each recurring connector can also be run manually to create a single instance of the entity being imported.