What exactly does Relis extract from my Bubble app?

Relis extracts four major components: Data Structure (Data Types, fields, Privacy Rules, Option Sets), API Connector (authentication, headers, parameters, endpoints), Backend Workflows (triggers, steps, conditions, parameters), and App Settings (privacy, appearance, API keys, SEO, language configurations).

What types of documents are generated?

Relis generates ERD Diagram, DDL Script (PostgreSQL/MySQL compatible), Table Specification, Data Dictionary, API Specification Document, Backend Workflow Documentation, Enum/Constants Definition, and full Markdown exports for each extraction category.

How is my Bubble app security ensured?

We only request Viewer access as a collaborator. We extract only structure and logic, never actual database records or user data. You can remove collaborator access anytime after analysis.

How long does the analysis take?

Analysis time varies: small apps take a few minutes, medium apps several minutes, and large apps with many APIs and workflows may take longer. You can monitor progress in real-time.

Can this help me migrate away from Bubble?

Yes. Relis creates a comprehensive blueprint for migration planning: ERD and DDL scripts for database setup, API documentation for external integrations, Backend Workflow docs for business logic, and App Settings docs for configuration reproduction.

Do I need to give edit access to my Bubble app?

No. Relis only requires Viewer access as a collaborator. We never modify your app, its data, or any settings. You remain in full control and can revoke access at any time.

What Bubble app sizes are supported?

Relis handles apps of all sizes — from simple MVPs to complex enterprise applications with hundreds of data types, dozens of API connections, and extensive backend workflows. Larger apps simply take a bit more time to analyze.

How is Relis different from manually documenting my Bubble app?

Manual documentation is time-consuming, error-prone, and quickly outdated. Relis extracts everything automatically with no missed fields or forgotten workflows, generates standardized formats (ERD, DDL, Markdown) that developers expect, and provides a consistent complete snapshot of your entire architecture.

Glossary

What is the Bubble.io API Connector?

The API Connector is Bubble.io's built-in plugin for making HTTP requests to external services — enabling integrations with payment gateways, email providers, analytics platforms, and any REST API through a visual configuration interface.

How It Works

HTTP Methods

Supports GET, POST, PUT, PATCH, and DELETE requests with full control over request bodies and query parameters.

Authentication

Handles API keys, Bearer tokens, OAuth 2.0, and custom header-based auth schemes through visual configuration.

Dynamic Parameters

Parameters can be marked as dynamic, letting workflows pass values at runtime rather than hardcoding them.

Response Mapping

JSON responses are mapped to Bubble data types, making external data available throughout the application.

Common Integrations

Stripe — Payment intents, subscriptions, customer management, and webhook handling for billing flows.
SendGrid and Mailgun — Transactional email sending, template rendering, and delivery status tracking.
Twilio — SMS notifications, phone verification, and voice call initiation from backend workflows.
Google APIs — Maps, Calendar, Sheets, and Drive integrations for productivity and location features.

Migration Challenges

Implicit Auth Flows — OAuth tokens managed by Bubble are invisible to developers — the migration must reconstruct the full auth flow from scratch.
Hardcoded Endpoints — API base URLs and paths are often embedded in connector configs with no environment variable support.
Rate Limiting — Bubble abstracts rate limit handling; migrated code must implement retry logic and backoff strategies explicitly.
Response Shape Assumptions — Bubble workflows assume specific response structures that may break if the external API changes its schema.

Migration Mapping

axios (Node.js / React) — Each API Connector call maps to an axios instance with interceptors for auth headers and error handling.
Faraday (Ruby) — Faraday middleware stacks replicate Bubble's auth, retry, and response parsing behavior.
requests (Python) — Session objects with mounted adapters mirror the connector's shared authentication configuration.
Guzzle (PHP) — Guzzle's handler stack and middleware system provides equivalent request/response transformation.

Related Terms

Backend workflowsBubble migrationBubble plugin dependencyReverse engineering

How Relis Extracts API Connectors

Relis extracts every API Connector configuration from your Bubble application — endpoints, authentication schemes, headers, parameters, and response mappings — and generates an OpenAPI-compatible specification your team can use to rebuild integrations in any stack.

See How It Works Try Relis Free