Integrate GitLab Data into Power Automate Desktop using CData Connect

CData Connect enables you to access live GitLab data in workflow automation tools like Power Automate. This article shows how to integrate GitLab data into a simple workflow, saving GitLab data into a CSV file.

CData Connect provides a live interface for GitLab, allowing you to integrate with live GitLab data in Power Automate — without replicating the data. Connect uses optimized data processing out of the box to push all supported SQL operations (filters, JOINs, etc) directly to GitLab, leveraging server-side processing to quickly return GitLab data.

Configure GitLab Connectivity for Power Automate

Connectivity to GitLab from Power Automate is made possible through CData Connect AI. To work with GitLab data from Power Automate, we start by creating and configuring a GitLab connection.

1. Log into Connect AI, click Sources, and then click Add Connection

2. Select "GitLab" from the Add Connection panel

3. Enter the necessary authentication properties to connect to GitLab.

   To connect to GitLab, use either OAuth or a personal access token:

   Using OAuth

   Register an OAuth application in GitLab under Edit Profile > Applications (or group Settings > Applications). Set the Redirect URI to https://oauth.cdata.com/oauth/. Note the Application ID (OAuth Client Id) and Secret (shown once). Then set:

   • OAuth Client Id: The Application ID from your GitLab OAuth application.
   • OAuth Client Secret: The Secret from your GitLab OAuth application.

   Click Sign In to complete OAuth authentication.

   Using a Personal Access Token

   In GitLab, navigate to Edit Profile > Access Tokens > Add new token. Select the required scopes (such as api, read_api, read_user, read_repository) and set an expiration date. Copy the token immediately (shown only once). Then set:

   • API Key: The personal access token from your GitLab account.
   
4. Click Save & Test
5. Navigate to the Permissions tab in the Add GitLab Connection page and update the User-based permissions.

Add a Personal Access Token

When connecting to Connect AI through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect AI. It is best practice to create a separate PAT for each service to maintain granularity of access.

1. Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
2. On the Settings page, go to the Access Tokens section and click Create PAT.
3. Give the PAT a name and click Create.
4. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.

With the connection configured and a PAT generated, you are ready to connect to GitLab data from Power Automate Desktop.

Integrate GitLab Data into Power Automate Workflows

After configuring CData Connect with GitLab, you are ready to integrate GitLab data into your Power Automate workflows. Open Microsoft Power Automate, add a new flow, and name the flow.

In the flow editor, you can add the options to connect to GitLab, query GitLab using SQL, and write the query results to a CSV document.

Add an Open SQL Connection Action

Add an "Open SQL connection" action (Action -> Database) and click the option to build the Connection string. In the Data Link Properties wizard:

1. On the Provider tab: select Microsoft OLE DB Driver for SQL Server
2. On the Connection tab:
   1. Select or enter a server name: set to tds.cdata.com,14333
   2. Enter information to lag onto the server: select "Use a specific username and password"
      • Set User name to your CData Connect AI user name (e.g. [email protected])
      • Set Password to your PAT
      • Select the database: use the database configured above (e.g. API1)
3. Click "Test Connection" to ensure the connection is configured properly
4. Click "OK"

After building the connection string in the Data Link Properties wizard, save the action.

Add an Execute SQL Statement Action

Add an "Execute SQL statement" action (Action -> Database) and configure the properties.

• Get connection by: SQL connection variable
• SQL connection: %SQLConnection% (the variable from the "Open SQL connection" action above)
• SQL statement: SELECT * FROM AccessRequests

After configuring the properties, save the action.

Add a Write to CSV File Action

Add a "Write to CSV file" action (Action -> File) and configure the properties.

• Variable to write to: %QueryResult% (the variable from the "Execute SQL statement" action above)
• File path: set to a file on disk
• Configure Advanced settings as needed.

After configuring the properties, save the action.

Add a Close SQL Connection Action

Add a "Close SQL connection" action (Action -> Database) and configure the properties.

• SQL Connection: %SQLConnection% (the variable from the "Open SQL connection" action above)

After configuring the properties, save the action.

Save & Run the Flow

Once you have configured all the options for the flow, click the disk icon to save the flow. Click the play icon to run the flow.

Now you have a workflow to save GitLab data into a CSV file.

With CData Connect AI, you get live connectivity to GitLab data within your Microsoft Power Automate workflows.

SQL Access to GitLab Data from Cloud Applications

Now you have a direct connection to live GitLab data from Power Automate tasks. You can create more connections and workflows to drive business — all without replicating GitLab data.

To get SQL data access to hundreds of SaaS, Big Data, and NoSQL sources directly from your cloud applications, sign up for a free trial of CData Connect AI.

Related Power Automate Articles

This article explains how to use CData Connect AI with Power Automate Desktop. Check out our other articles for more ways to work with Power Automate (Desktop & Online):

• GitLab Data in Power Automate (Online) using CData Connect AI