Sync leads to your own Supabase

Supabase sync sends your completed search results into a database you control, so you don’t have to move CSVs by hand. Run a search, and the results flow into your own Supabase project, ready to query, join, and build on.

This feature is available on the Pro and Business plans.

What Supabase sync does

Instead of exporting a CSV and importing it somewhere else, your leads land directly in a business_leads table in your own Supabase database. Each record carries the same fields gtme.business returns — name, full address, phone, website, Google rating, review count, category, GPS coordinates, business hours, price level, and a Google Maps link — so everything you’d get from an export is available to query in SQL.

Because the data lives in your database, you own it outright. You can connect it to your own app, dashboards, CRM pipelines, or internal tooling without an extra import step.

Setting up the connection

You’ll need a Supabase project and your project’s connection details. The setup runs once:

1. Create the business_leads table in your Supabase project. gtme.business provides the exact setup SQL to run in your Supabase project’s SQL Editor.
2. Provide your Supabase Project URL (for example, https://abc123.supabase.co).
3. Provide your Supabase service role key.
4. Connect.

You can find your project URL and service role key in your Supabase dashboard under Settings → API Keys. The business_leads table is validated before your credentials are saved, so a missing or mismatched table is caught up front rather than failing silently later.

How sync works

Once connected, searches sync to your Supabase database automatically:

• Results sync in batches of 500 rows.
• Sync runs in the background once durable output is ready, so it doesn’t hold up your search.
• Searches you completed before connecting are queued for sync when you first connect, so earlier work isn’t left behind.
• Failed syncs are retried automatically.
• Duplicate businesses are handled by upsert — existing records are updated in place rather than duplicated, so re-running a search won’t bloat your table with copies.

The upsert behavior matters most for recurring work. If you re-scrape a city to catch new openings or refreshed ratings, the table stays clean: new businesses are inserted, known ones are updated, and you avoid the manual dedupe pass a CSV workflow usually requires.

Keeping an eye on sync

After connecting, you can see your current connection status, the time of the most recent sync, and recent sync history with row counts — enough to confirm that each search reached your database and how many rows it wrote.

Disconnecting

You can disconnect at any time to stop future syncs. Data already written to your Supabase database isn’t touched — disconnecting only stops new results from syncing. Reconnect later and gtme.business picks up where you left off.

Where it fits

Supabase sync is built for data teams and anyone running leads through their own systems rather than a spreadsheet. If you’re scraping the same markets on a schedule, the combination of background sync and upsert dedupe keeps a single, current source of truth without manual cleanup.

New accounts start free and no card required, so you can test a full search end to end before deciding on a plan. See how it works for the search-and-export basics, or create an account to get started.