Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.nekt.com/llms.txt

Use this file to discover all available pages before exploring further.

Bubble is a no-code platform for building web applications. It allows users to create custom databases, workflows, and user interfaces without writing code. The Bubble Data API provides access to all application data types and their records.

​
Configuring Bubble as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Bubble option from the list of connectors. Click Next and you’ll be prompted to add your access.

​
1. Add account access

You’ll need to provide your Bubble Data API key and app details. The following configurations are available:
  • API Key: Your Bubble Data API key (bearer token). You can find it in your Bubble app under Settings > API > Data API. Make sure the Data API is enabled and the key has read access to the data types you want to sync.
  • App Name: Your Bubble app subdomain. For example, if your app URL is myapp.bubbleapps.io, enter myapp.
  • Data Types: A list of Bubble data type names you want to sync. Enter the exact names as they appear in your Bubble database (e.g., user, order, product). Each data type will become a separate stream.
  • Custom Domain (optional): If your Bubble app uses a custom domain instead of the default bubbleapps.io, enter it here (e.g., app.example.com).
  • Environment (optional): Choose between live (production data) or test (development data). Defaults to live.
  • Start Date (optional): The earliest date from which records will be synced. Only applicable for incremental sync.
Once you’re done, click Next.

​
2. Select streams

Choose which data streams you want to sync. Each configured data type appears as a separate stream. For faster extractions, select only the streams that are relevant to your analysis. Select the streams and click Next.

​
3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, only new or modified records are fetched, based on the Modified Date field.
    • Full table: every time the extraction happens, the current state of all records is fetched.
Once you are done configuring, click Next.

​
4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. Once you are ready, click Next to finalize the setup.

​
5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

​
Streams and Fields

Streams are dynamically created based on the data types you configure. Every Bubble data type includes the following base fields:
FieldTypeDescription
_idstringUnique record identifier
Created DatedatetimeWhen the record was created
Modified DatedatetimeWhen the record was last modified
Created BystringUser who created the record
SlugstringURL-friendly identifier
Additional fields from your Bubble data types are automatically included in the sync. Fields with complex types (objects, lists) are serialized as JSON strings.
Since Bubble data types are user-defined, the specific fields available depend on your application’s database schema. Ensure the data types listed in your configuration exactly match the names in your Bubble database.