The Lyftron Provider for Zenkit offers the most natural way to access Zenkit data from Lyftron with ease and also enables to connect with BI, MDM & ML tools, Data warehouses, Databases and other SAAS based applications with zero code and zero infrastructure requirements. The provider wraps the complexity of accessing Zenkit data into easy-to-integrate relational fully managed ANSI Sql format. Make faster and better business decisions with Lyftron’s Zenkit data provider and automatically build your data migration pipelines in minutes, not months
The provider hides the complexity of accessing data and provides additional powerful security features, smart caching, batching, socket management, and more.
- Comprehensive Delta load mechanism.
- Real-time access to Zenkit.
- Comprehensive full support of ANSI Sql to query data with ease.
- Collaborative query processing.
The user must have credentials for Zenkit, Lyftron and your destination data warehouse, lake or database to perform the data pipeline operation with Lyftron
Establishing a Connection with Lyftron's Quickstart Steps
Create your Zenkit connection with Lyftron by following the 5 easy steps show below:
Step1. Add your connection
Click on Connect section on the left panel → Click on Add Connection button
Step2. Select your connector
In the connector selection panel, search and click Zenkit for your connection
Step3. Enter your connection details
In the Connection String section enter the values of the below parameters. The following connection string is required to establish Zenkit connection with Lyftron."Profile=C:\profiles\Zenkit.apip;ProfileSettings='Authscheme=OAuth;InitiateOAuth=GETANDREFRESH;OAuthClientId=your_client_id;OAuthClientSecret=your_client_secret;CallbackUrl=your_callback_url';"
|Connection Name||Enter your connection details||Required|
|OAuthClientId||Your client id||Required|
|OAuthClientSecret||Your client secret||Required|
|CallbackUrl||Your callback URL||Required|
|Logfile**||Use the logfile option to debug your job and provide your connection name to generate the log file. [ConnectionConfigurationPath]\Connection_name_log.tx||Optional|
|Verbosity**||Choose verbosity 1-5 based on the severity of debugging||Optional|
** For more information, check the Lyftron logging and debugging section.
If you want more detailed information about how to establish a connection with Lyftron, click on Lyftron Connection Quick Start guide.
Step4. Test your connection
Once you are done entering your connection details, simply click on the Test Connection button to test the connectivity. In case your connection fails, add Logfile and Verbosity parameters and check the Lyftron logging and debugging section, to debug the error.
Step5. Save your connection
The provider models the data in API into a list of tables that can be queried using standard SQL statements.
Generally, querying API tables is the same as querying a table in a relational database. Sometimes there are special cases, for example, including a certain column in the WHERE clause might be required to get data for certain columns in the table. This is typically needed for situations where a separate request must be made for each row to get certain columns.
|CurrentUser||Table||Get the current user.|
|ElementCategories||Table||Get accesses for the user.|
|Entry||Table||Get a specific list entry.|
|ListActivities||Table||Returns list activities.|
|ListElements||Table||Get all elements in a list.|
|ListEntries||Table||Get filtered/grouped list entries for list view.|
|ListEntryActivities||Table||Returns list entry activities.|
|Lists||Table||Get all the lists for the user.|
|UserAccess||Table||Get accesses for the user.|
|UserActivities||Table||Returns the user's activities.|
|WorkspaceActivities||Table||Returns workspace activities.|
|Workspaces||Table||Get all workspaces for the user.|
|WorkspaceUsers||Table||Get all users with access to the workspace.|
To view a detailed advanced settings options, go to Zenkit Advanced Settings. Complete list of the parameters you can configure in the connection string can be found by clicking Connection String Parameters.