Bubble App Connector
Last updated
Was this helpful?
Last updated
Was this helpful?
The App Connector connects two Bubble apps and accesses the API and data of one app in another. By doing so, you can sign up with OAuth with another app, run workflows as the user, etc.
To make this work, set up an API with the first app A before using it in app B. To enable users to sign up with app A in app B, define some OAuth credentials in app A. Once this is done, install the Bubble App Connector and add app A in app B.
Once you've added an app and installed some calls, you can use them either as a data source in 'Get data from API' or as actions in workflows.
Enter the domain of the app. It should be similar to or , i.e., without a page. Using this domain, Bubble will automatically fetch the metadata of the app.
Note: Be sure to use the bare domain (no 'www'), as including the 'www' can lead to unexpected behavior when using the App Connector in workflows.
Check this box when you want the developer environment of app A to interact with the developer environment of app B. Typically, this box is checked.
This is how to describe the app within the Bubble Editor. By default, this is the app name, but it can be renamed. This is important when referring to the different calls in the Bubble Editor.
Enter the Private key generated in the API section in the Settings Tab of the app you want to connect with.
Enter the Client ID of the app for OAuth purposes.
Enter the Client secret of the app for OAuth purposes.
Select the call to install. It can either be an API Workflow or GET call.
Select whether to use the call as a data source or action. Normally, API Workflows will be actions, and GET calls will be data sources, but in some cases it may be different. For example, when an API Workflow returns data.
Select which type of authentication you want to call to run. If you select Private key, it will run as an admin in the second app. If you select OAuth and enter a Client ID and Client secret, calls will run as the current user after signing up with OAuth. In this case, privacy rules, etc. will apply as the user. No authentication will run calls without any credentials.
To modify both apps at the same time, click this button to refresh the data.
When you get started with the App Connector, you will have 2 apps:
App A (which can be your main app)
App B (which can be your sub app and you can add as many as you like)
App A (main) is where most data operations and workflow executions usually happen. App A will be where the data is stored and data needs to be exposed through an endpoint while App B (sub) is used to drive those workflows and pull data from App A (main).
First, we start by setting up app A (main) to give us the right access level (Private Key), allow sharing workflows (expose workflow API) and data (expose Data API), and something like an ID card to tell App A who is talking to it (Client ID & Secret). Then in App A (main) you setup actual workflows to signup but it can be other workflows too like charging a customer or sending them emails. Next, you use the App Connector plugin in App B (sub) to control A (main) by showing your ID, confirming your access level and then telling it what to do.
Here is how we make this happen:
In App A settings > API tab, enable ‘"This app exposes a Data API" and "Workflow API." Create a new API token and notice the Private Key, then set the login page as the one containing your signup popup.
Add a new 3rd party app with name (such as app B’s name) and Redirect URI which should be the landing page back in App B.
Notice Client ID and Secret – you will need this later.
Add a new Bubble app within the plugin with following details:
App domain: yourappname.bubbleapps.io (use custom domain if applicable)
Enable match versions
Private key – get from previous step
Client ID & Secret – get from previous step
Set the workflow to account > signup/login with a social network, then choose "Bubble app - app name" as the OAuth provider.
Try App B in run-mode > click login > you will get redirected to signup page on App A. Once logged in, you will get redirected to App B landing page and the user’s login details will be stored on both apps. Note that login is "User" type data that is special in that it gets stored in both apps. Any workflows you drive from the App Connector for App A (main) will run in App A and store data only in App A.
If you want to pull non-user Data from App A (main) into App B (sub), the "expose Data API" will now be useful. You will expose that data type from App A (main) settings and then be able to select it from the app connector under add a call / Installed calls and then use it in elements within App B (sub) like any other "Do a search."
For each call in step 7, select "Action" in "Use as" for workflows and ‘"Data" for pulling a data type.
For both workflows and data, typically set authentication as "OAuth" as this requires user signup and sets access through roles defined in the Privacy Settings of the app while "API key" grants admin access and "none" gives bare minimum access.
Note: When using the API Connector or App Connector, parameters currently cannot be a 'raw' list of Bubble Things, e.g. a dynamic statement that results in a List of Things. This is because a raw list of Bubble Things is not rendered in the kind of text formatting that API endpoints expect. One workaround for this is to use the ":join with" operator on the list of Bubble Things to turn it into a format accepted by the API endpoint (this is likely a format like ["first thing", "second thing"]).
