SuggestAPISuggestAPI
Integrations

Catalog source

Turn a Supabase table into a search index.

Link the project, pick a table, and map columns. SuggestAPI pulls those rows into an index on a schedule so shoppers and agents can search them. The table stays in Supabase.

Diagram of a Supabase table mapped by id, title, and description, synced hourly or daily into a SuggestAPI search index used by a shopper and an agent.

  1. 01

    Link the project

    Connect the Supabase project from Integrations. SuggestAPI reads it. It does not become your database.

  2. 02

    Pick the table

    Choose the database, schema, and table or view that holds the records you want searchable.

  3. 03

    Map the columns

    Point id at the row key. Map title, description, and manufacturer when those columns exist.

  4. 04

    Sync into an index

    Send the mapped rows into a SuggestAPI index on a schedule: manual, hourly, or daily.

What the sync keeps current

  • The table stays put

    Rows remain in Supabase. Search runs against the index SuggestAPI builds from them.

  • Changes catch up

    A table with updated_at syncs only rows that changed. Without that column, the next run pulls the table again.

  • Removed rows drop out

    Each sync checks source ids and prunes index documents that no longer exist in the table.

This is a scheduled pull, not a live query of Postgres on every keystroke, and not change-data capture. Search uses the index. Supabase remains the source of the rows.

Sign up