Build SingleStore-Connected Apps in Bubble

Bubble is a no-code platform that simplifies the process of developing and launching apps and businesses. When coupled with CData Connect AI, you gain effortless no-code access to SingleStore data for streamlined app development. This article guides you through the integration process from Bubble to SingleStore using CData Connect AI.

CData Connect AI provides a pure cloud-to-cloud OData interface for SingleStore data that allows you to integrate from Bubble to SingleStore data in real time.

Connect to SingleStore from Bubble

To work with SingleStore data from Bubble, we need to connect to SingleStore from Connect AI, provide user access to the connection, and create a Workspace for the SingleStore data.

Connect to SingleStore from Connect AI

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

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

2. Select "SingleStore" from the Add Connection panel
👁 Selecting a data source

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

   The following connection properties are required in order to connect to data.

   • Server: The host name or IP of the server hosting the SingleStore database.
   • Port: The port of the server hosting the SingleStore database.
   • Database (Optional): The default database to connect to when connecting to the SingleStore Server. If this is not set, tables from all databases will be returned.

   Connect Using Standard Authentication

   To authenticate using standard authentication, set the following:

   • User: The user which will be used to authenticate with the SingleStore server.
   • Password: The password which will be used to authenticate with the SingleStore server.

   Connect Using Integrated Security

   As an alternative to providing the standard username and password, you can set IntegratedSecurity to True to authenticate trusted users to the server via Windows Authentication.

   Connect Using SSL Authentication

   You can leverage SSL authentication to connect to SingleStore data via a secure session. Configure the following connection properties to connect to data:

   • SSLClientCert: Set this to the name of the certificate store for the client certificate. Used in the case of 2-way SSL, where truststore and keystore are kept on both the client and server machines.
   • SSLClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
   • SSLClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
   • SSLClientCertType: The certificate type of the client store.
   • SSLServerCert: The certificate to be accepted from the server.

   Connect Using SSH Authentication

   Using SSH, you can securely login to a remote machine. To access SingleStore data via SSH, configure the following connection properties:

   • SSHClientCert: Set this to the name of the certificate store for the client certificate.
   • SSHClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
   • SSHClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
   • SSHClientCertType: The certificate type of the client store.
   • SSHPassword: The password that you use to authenticate with the SSH server.
   • SSHPort: The port used for SSH operations.
   • SSHServer: The SSH authentication server you are trying to authenticate against.
   • SSHServerFingerPrint: The SSH Server fingerprint used for verification of the host you are connecting to.
   • SSHUser: Set this to the username that you use to authenticate with the SSH server.
   👁 Configuring a connection (Salesforce is shown)
   
4. Click Save & Test
5. Navigate to the Permissions tab in the Add SingleStore Connection page and update the User-based permissions. 👁 Updating 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. 👁 Creating a new PAT
   
4. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.

Configure SingleStore Endpoints for Bubble

After connecting to SingleStore, create a workspace for your desired table(s).

1. Navigate to the Workspaces page and click Add to create a new Workspace (or select an existing workspace). 👁 The Workspaces page.
   👁 Adding a new Workspace.
   
2. Click Add to add new assets to the Workspace.
3. Select the SingleStore connection (e.g. SingleStore1) and click Next. 👁 Selecting an Asset (Salesforce is shown).
   
4. Select the table(s) you wish to work with and click Confirm. 👁 Selecting Tables (Salesforce is shown).
   
5. Make note of the OData Service URL for your workspace, e.g. https://cloud.cdata.com/api/odata/{workspace_name}

With the connection, PAT, and Workspace configured, you are ready to connect to SingleStore data from Bubble.

Build a SingleStore-Connected App

With OData endpoints added to Connect AI, you can build an app in Bubble with live access to SingleStore data.

Configure the Bubble API Connector

To start, Configure the API Connector for accessing CData Connect AI from Bubble.

1. In your app, click the Plugins tab and click Add plugins
2. Search for "API Connector" and click Install 👁 Installing the API Connector plugin
   
3. After installation, click the "Add another API" button and configure the API:
   • Name the API
   • Set Authentication to "HTTP Basic Auth"
   • Set Username to a Connect AI user (e.g. [email protected])
   • Set Password to the PAT for the user
   • Expand the API Call, select the "GET" command and set the URL to a Workspace endpoint you previously configured (e.g. https://cloud.cdata.com/api/odata/{workspace_name}/Orders)
   👁 Configuring the API Call
   
4. Click the "Initialize call" button to adjust data types in the response (as needed) 👁 Initializing the call
   
5. After making any necessary changes, click "Save" 👁 Saving the data types
   

Configure the App UI

With the API Connector configure, you are ready to retrieve SingleStore data in your Bubble app. In this article, we request the data with a UI component that can display an Excel-like table.

1. On the Plugin tab, install the "Excel-like HandsonTable" 👁 Adding the Excel-like HandsonTable plugin
   
2. On the Design tab, add an "Excel Table" to the workspace 👁 Adding an Excel Table to the app
   
3. In the Excel Table, in Data source, select "Get data from an external API"
4. Set Type of content to "API Call value"
5. Set Data source to "CData Connect AI - API Call's value" (or equivalent) 👁 Binding the Excel Table to the API Call
   
6. Click "Preview" to ensure the data was retrieved from SingleStore. 👁 Previewing the app
   

At this point, you can develop applications with live access to SingleStore data without needing to know the complexities of the back-end API.

Live Access to SingleStore Data from Cloud Applications

Now you have a direct connection to live SingleStore data from Bubble. You can create more SingleStore-connected apps — all without writing any code or replicating SingleStore data.

To get live data access to hundreds of SaaS, Big Data, and NoSQL sources directly from your cloud applications, see the CData Connect AI.