Skip to main content
Autopilot uses the same trigger-based database connection as self-serve Dreamlit. It needs a reachable Supabase or Postgres database, a dedicated dreamlit_app user, and permission to manage its own dreamlit schema. It never changes your app’s rows.

What does Dreamlit install?

Connection setup creates a dreamlit schema with event_log, error_log, and version tables for workflow events, logging, and schema management. Verification checks that Dreamlit can read your allowed tables, create triggers, and read and write its internal tables. Publishing a database-triggered workflow installs a trigger on the chosen table. When the configured change occurs, the trigger records an event in dreamlit.event_log. Dreamlit polls these events and starts the workflow. Unpublishing removes the trigger and stops new runs; runs already in progress need to be canceled separately. Recurring workflows use a schedule. Broadcasts run once at the selected time. Supabase Auth emails use an explicitly enabled auth hook.

Which permissions are required?

  • Read access to the application tables needed for targeting, personalization, previews, and lifecycle analysis.
  • Trigger permission on tables used by database-triggered workflows.
  • Permission to create and manage Dreamlit’s own schema and internal tables.
For cloud-hosted Supabase, Supabase Connect provisions the dedicated user, grants, and helper functions. For other Postgres providers, you create the user and grant permissions yourself. Use the Supabase guide or the Postgres guide rather than a replication role. Logical replication is not required.

What data is processed and retained?

Dreamlit queries live data for previews, audiences, personalization, and reports. Workflow runs retain the state needed to execute their steps. Notification analytics retain delivery and engagement activity, including per-recipient history. Event and error logs also live in the Dreamlit-managed schema. These are separate from your application rows, which Dreamlit doesn’t edit. See security and the privacy policy for more detail. Contact support for retention requirements specific to your account.

What happens during an outage?

Events successfully recorded in dreamlit.event_log can wait for Dreamlit to reconnect. Workflow steps retry transient failures. Trigger failures, revoked permissions, deleted logs, or a database outage can interrupt processing, so this isn’t a guarantee that every event is captured or every message is delivered exactly once. Check the Activity Log for failed runs and system status for incidents. For performance planning, account for trigger writes and the reads your previews and workflow queries make against the database.

How do I remove the connection?

Unpublish dependent workflows, delete the connection in Dreamlit, then follow the Postgres uninstall instructions if you also want to remove the internal schema and user.