Confluence

The Lyftron Provider for Confluence offers the most natural way to access Confluence 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 Confluence data into easy-to-integrate relational fully managed ANSI Sql format. Make faster and better business decisions with Lyftron’s Confluence 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.

Key Features

• Comprehensive Delta load mechanism.
• Real-time access to Confluence.
• Comprehensive full support of ANSI Sql to query data with ease.
• Collaborative query processing.

Prerequisites

The user must have credentials for Confluence, 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 Confluence 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 Confluence 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 Confluence connection with Lyftron.

"User=admin;APIToken=myApiToken;Url=https://yoursitename.atlassian.net;Timezone=America/New_York;"

Key	Value	Field
Connection Name	Enter your connection details	Required
User	admin	Required
APIToken	Your Confluence APIToken	Required
Url	https://yoursitename.atlassian.net	Required
Timezone	America/New_York	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

Hurray! Now you have successfully connected with the Lyftron Confluence connector and can utilize the connector to Extract, Warehouse, Analyze, Visualize and Share your data.

Data Model

Views are composed of columns and pseudo columns. Views are similar to tables in the way that data is represented; however, views do not support updates. Entities that are represented as views are typically read-only entities. Often, a stored procedure is available to update the data if such functionality is applicable to the data source.

Queries can be executed against a view as if it were a normal table, and the data that comes back is similar in that regard.

Name	Type	Description
Attachments	Views	Get information about a specific attachment.
AuditRecords	Views	Fetch a paginated list of AuditRecord instances dating back to a certain time.
Blogposts	Views	Get information about a specific blogpost.
Comments	Views	Get information about a specific comment.
Contributors	Views	Get information about the users who have contributed to the content.
Groups	Views	Get information about a specific group.
Labels	Views	Get information about the labels that a specific content has.
Pages	Views	Get information about a specific page.
Spaces	Views	Returns information about a number of spaces.
Users	Views	Get information about a user identified.