Bi-directional connector that syncs Supabase database tables, Storage files, and organization members into DevRev. Schema-agnostic design works with any project structure.

Sync Supabase databases, Storage, organization members, and security policies with DevRev. AI agents can search, synchronize, and manage structured data and documents while keeping DevRev and Supabase in sync.

Features

• Database synchronization Import PostgreSQL tables as DevRev custom objects (default) with automatic schema discovery and column-to-field mapping, or map tables to DevRev stock objects such as Account, Contact, and Opportunity. This is useful when your Supabase database already models CRM-style data. Supports incremental synchronization using timestamp columns.
• Storage integration Sync Supabase Storage buckets and folders into DevRev. Documents such as PDFs, Word files, Excel spreadsheets, and Markdown files become searchable articles, while other files are imported as artifacts.
• Organization member sync Import Supabase organization members as DevRev dev users by matching email addresses. Members are grouped by project and granted access to shared content.
• Bi-directional synchronization Keep DevRev and Supabase synchronized by writing create, update, and delete operations from DevRev back to PostgreSQL through PostgREST.
• Row-Level Security audit Import Row-Level Security (RLS) policies as DevRev custom objects to create a searchable inventory of database access rules and security policies.

 

Use Cases

• Engineering teams Sync operational PostgreSQL data into DevRev, making application data searchable and actionable without leaving your workflow.
• Sales and CRM teams Map Supabase tables such as accounts, contacts, and opportunities directly to DevRev stock objects so CRM data behaves natively in DevRev instead of living as separate custom objects.
• Support teams Surface documents and files stored in Supabase Storage as searchable articles, enabling faster issue resolution.
• Platform administrators Audit Row-Level Security policies and database access rules from a centralized, searchable inventory.
• Cross-functional teams Keep business data synchronized between Supabase and DevRev so AI agents and workflows always work with the latest information.

 

Access

Connect your Supabase project using a service role key. The connector requires read access to your PostgreSQL database, Storage buckets, organization members, and Row-Level Security (RLS) policies to import data into DevRev. If bi-directional synchronization is enabled, it also requires write access to your PostgreSQL database through PostgREST. Organization members are imported as DevRev dev users using email matching, and the connector respects your existing Supabase permissions and RLS policies.