Quick-start (2 minutes)
⸻

1️⃣ Create the required data types in your Bubble app

AppEnvironment
• key (text, unique – e.g. dev, staging, prod)
• is_active (yes/no)
• description (text, optional)

ConfigVariable
• key (text, unique – e.g. features.new_checkout)
• value_type (text: text, number, or boolean)
• default_value_text (text, optional)
• default_value_number (number, optional)
• default_value_boolean (yes/no, optional)
• description (text, optional)

Only one default value should be used, matching value_type.

ConfigValue
• environment (AppEnvironment)
• variable (ConfigVariable)
• value_text (text, optional)
• value_number (number, optional)
• value_boolean (yes/no, optional)
• is_active (yes/no)

⸻

2️⃣ Configure the plugin

In the plugin settings, add:
• Bubble Data Base URL
https://yourapp.bubbleapps.io/version-test/api/1.1/obj
• Bubble API Key
(Settings → API → Data API, for the same environment)

Enable the Data API in your app.

Requires a Bubble plan with Data API access (Growth or higher).

⸻

3️⃣ Define your environments and variables

Example:
• Environment: dev
• Environment: prod
• Variable: features.new_checkout
• type: boolean
• default: false
• Variable: limits.max_users
• type: number
• default: 10

⸻

4️⃣ Define environment-specific values

Example:
• dev → features.new_checkout = true
• prod → features.new_checkout = false
• prod → limits.max_users = 100

Leave values undefined in other environments to fall back to defaults.

⸻

5️⃣ Read configuration values in a workflow

In any workflow or backend workflow:
1. Add the action Get Config Value
2. Pass:
• environment_key → e.g. dev or prod
• variable_key → e.g. features.new_checkout
3. Use the returned value:
• value_text
• value_number
• or value_boolean (based on value_type)
4. If found = no:
• handle explicitly
• or fail closed

That’s it.