Integrate Bitbucket Data into Automated Tasks with Power Automate



Use CData Connect Server to create a virtual SQL Server database for Bitbucket data and integrate live Bitbucket data into your Power Automate (Microsoft Flow) tasks.

Power Automate (Microsoft Flow) is an online service that automates events (known as workflows) across the most common apps and services. When paired with CData Connect Server, you get instant, cloud-to-cloud access to Bitbucket data for visualizations, dashboards, and more. This article shows how to connect to Connect Server from Power Automate and integrate live Bitbucket data into your workflows and tasks.

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

Create a Virtual SQL Database for Bitbucket Data

CData Connect Server uses a straightforward, point-and-click interface to connect to data sources and generate APIs.

  1. Login to Connect Server and click Connections.
  2. Select "Bitbucket" from Available Data Sources.
  3. Enter the necessary authentication properties to connect to Bitbucket.

    For most queries, you must set the Workspace. The only exception to this is the Workspaces table, which does not require this property to be set, as querying it provides a list of workspace slugs that can be used to set Workspace. To query this table, you must set Schema to 'Information' and execute the query SELECT * FROM Workspaces>.

    Setting Schema to 'Information' displays general information. To connect to Bitbucket, set these parameters:

    • Schema: To show general information about a workspace, such as its users, repositories, and projects, set this to Information. Otherwise, set this to the schema of the repository or project you are querying. To get a full set of available schemas, query the sys_schemas table.
    • Workspace: Required if you are not querying the Workspaces table. This property is not required for querying the Workspaces table, as that query only returns a list of workspace slugs that can be used to set Workspace.

    Authenticating to Bitbucket

    Bitbucket supports OAuth authentication only. To enable this authentication from all OAuth flows, you must create a custom OAuth application, and set AuthScheme to OAuth.

    Be sure to review the Help documentation for the required connection properties for you specific authentication needs (desktop applications, web applications, and headless machines).

    Creating a custom OAuth application

    From your Bitbucket account:

    1. Go to Settings (the gear icon) and select Workspace Settings.
    2. In the Apps and Features section, select OAuth Consumers.
    3. Click Add Consumer.
    4. Enter a name and description for your custom application.
    5. Set the callback URL:
      • For desktop applications and headless machines, use http://localhost:33333 or another port number of your choice. The URI you set here becomes the CallbackURL property.
      • For web applications, set the callback URL to a trusted redirect URL. This URL is the web location the user returns to with the token that verifies that your application has been granted access.
    6. If you plan to use client credentials to authenticate, you must select This is a private consumer. In the driver, you must set AuthScheme to client.
    7. Select which permissions to give your OAuth application. These determine what data you can read and write with it.
    8. To save the new custom application, click Save.
    9. After the application has been saved, you can select it to view its settings. The application's Key and Secret are displayed. Record these for future use. You will use the Key to set the OAuthClientId and the Secret to set the OAuthClientSecret.
  4. Click Save Changes
  5. Click Privileges -> Add and add the new user (or an existing user) with the appropriate permissions.

Connecting to CData Connect Server

To use Connect Server to integrate Bitbucket data into your Power Automate tasks, you need a new SQL Server connection:

  1. Log in to Power Automate
  2. Click Data -> Connections -> New connection
  3. Select SQL Server
  4. In the connection wizard:

    • Set Authentication Type to "SQL Server Authentication"
    • Set SQL server name to the address of your Connect Server instance (connect_server_url)
    • Set SQL database name to the name of the virtual Bitbucket database you created earlier (like bitbucketdb)
    • Set the Username and Password and click Create

Integrating Bitbucket Data into Power Automate Tasks

With the connection to Connect Server configured, you are ready to integrate live Bitbucket data into your Power Automate tasks.

  1. Log in to Power Automate
  2. Click My flows -> New and choose to create the flow from blank or template
  3. Add (or configure) a SQL Server action (like Get rows) and configure the action to connect to your Connect Server connection
  4. Select a Table to work with (from the drop-down menu) and configure any advanced options (like filters, orders, etc)
  5. Configure any actions to follow and test, then save the flow

SQL Access to Bitbucket Data from Applications

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

To get SQL data access to 200+ SaaS, Big Data, and NoSQL sources directly from your applications, see the CData Connect Server.

Related Power Automate Articles

This article walks through using CData Connect Server with Power Automate (Online). Check out our other articles for more ways to work with Power Automate Desktop:

Ready to get started?

Learn more or sign up for a free trial:

CData Connect Server