Trigger Bitbucket IFTTT Flows in Azure App Service

Through standards-based interfaces like OData and Swagger, the CData API Server provides a native experience in Logic Apps and Power Automate with Bitbucket. OData enables real-time connectivity to data; Swagger enables scaffolding, or code generation, of wizards in Logic Apps and Power Automate, as well as scaffolding Power Apps. This article shows how to add Bitbucket to an IFTTT (if-this-then-that) workflow in a Logic App.

Set Up the API Server

If you have not already done so, download the CData API Server. Once you have installed the API Server, follow the steps below to begin producing secure Bitbucket OData services:

Connect to Bitbucket

To work with Bitbucket data in a Logic App, we start by creating and configuring a Bitbucket connection. Follow the steps below to configure the API Server to connect to Bitbucket data:

1. First, navigate to the Connections page.
2. Click Add Connection and then search for and select the Bitbucket connection.
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. After configuring the connection, click Save & Test to confirm a successful connection.

Configure API Server Users

Next, create a user to access your Bitbucket data through the API Server. You can add and configure users on the Users page. Follow the steps below to configure and create a user:

1. On the Users page, click Add User to open the Add User dialog.
2. Next, set the Role, Username, and Privileges properties and then click Add User.
3. An Authtoken is then generated for the user. You can find the Authtoken and other information for each user on the Users page:

Creating API Endpoints for Bitbucket

Having created a user, you are ready to create API endpoints for the Bitbucket tables:

1. First, navigate to the API page and then click Add Table .
2. Select the connection you wish to access and click Next.
3. With the connection selected, create endpoints by selecting each table and then clicking Confirm.

Gather the OData Url

Having configured a connection to Bitbucket data, created a user, and added resources to the API Server, you now have an easily accessible REST API based on the OData protocol for those resources. From the API page in API Server, you can view and copy the API Endpoints for the API:

Access Bitbucket in a Logic App

You can use the API Server in a Logic App to create process flows around Bitbucket data. The HTTP + Swagger action provides a wizard to define the operations you want to execute to Bitbucket. The following steps below show how to retrieve Bitbucket data in a Logic App.

If your table has a column containing the creation date of a record, you can follow the steps below to write a function to check the column values for any new records. Otherwise, skip to the Create a Logic App section to send out emails to entities that match a filter.

Check for New Bitbucket Entities

To find new Bitbucket entities since a certain time, you can write a function that retrieves a datetime value for the start of the interval:

1. In the Azure Portal, click New -> Function App -> Create.
2. Enter a name and select the subscription, resource group, App Service plan, and storage account.
3. Select your Function App and select the Webhook + API scenario.
4. Select the language. This article uses JavaScript.
5. Add the following code to return the previous hour in a JSON object:

   module.exports = function (context, data) { 
     var d = new Date();
     d.setHours(d.getHours()-1); 
     // Response of the function to be used later.
     context.res = { 
       body: { 
         start: d 
       } 
     }; 
     context.done(); 
   };
   

Add Bitbucket to a Trigger

Follow the steps below to create a trigger that searches Bitbucket for results that match a filter. If you created the function above, you can search for objects that were created after the start of the interval returned.

1. In the Azure Portal, click New and in the Web + Mobile section select Logic App and select a resource group and App Service plan.
2. You can then use the wizards available in the Logic App Designer, which can be accessed from the settings blade for the Logic App. Select the Blank Logic App template.
3. Add a Recurrence action that will poll for the Bitbucket objects. This article polls every hour. Select the timezone -- the default is UTC.
4. Add a function action: Expand the menu in the Add Action dialog and select the option to show Azure functions in the same region. Select the Function App you created earlier and select the function that returns the interval start.
5. Enter an empty pair of curly brackets, "{}", to pass an empty payload object to the function.
6. Add the HTTP + Swagger action and enter the swagger URL of the API Server:

   http://MySite:MyPort/api.rsc/@MyAuthtoken/$oas

7. Select the "Return Issues" operation.

8. Use the descriptions for each property to specify additional parameters such as the columns to retrieve, filters, etc. Below is an example filter:

   Id eq '1'

   The API Server returns the descriptions and other documentation in the swagger document. You can find more information on using the OData API and supported OData in the API Server help documentation.

9. To use the datetime value returned from the getInterval function, use the "ge" operator with a datetime column in the Issues table and select the Body parameter in the dialog. Note that quotes must be used to surround the datetime value.

   

10. Switch to Code View and modify the $filter expression to extract the property containing the start of the interval. Use the syntax '@{body('MyFunc')['MyProp']'.

    "getAllAccount": {
      "inputs": {
        "method": "get",
          "queries": {
            "$filter": "CreatedDate ge '@{body('getInterval')['start']}'"
          },
          "uri": "https://MySite:MyPort/api.rsc/@MyAuthtoken/Issues"
      }
    

You can now access Bitbucket as data sources and destinations in your workflows.

Email New Records

Follow the steps below to email a report with any new Issues entities.

1. In the Logic Apps Designer, add an SMTP - Send Email action.
2. Configure the necessary information for the SMTP server.
3. Configure the From, To, Subject, and Body. You can add parameters from the Bitbucket columns returned.

Click Save and then click Run to send email notifications on any Bitbucket records created in the last hour.