Forms and data integration
Import recipients from Supabase
Connect a Supabase project URL and secret key, choose a table or view in the public schema, then map its columns to recipient name, email and certificate Attributes.
Import
Your database is the source of truth
Useful when registrations already live in an application database and a spreadsheet export would be a stale copy.
- 01
Connect the project
Enter the project URL and a secret key. Verifycate checks the REST endpoint before saving the connection.
- 02
Choose a table or view
Tables and views in the public schema are listed. A view can pre-filter, join or rename columns so the import matches your certificate Attributes.
- 03
Map and import
Columns map by name to name, email and Attributes. Verifycate validates the rows, and you can save the mapping to reuse the same pull later.
Read-only by design
Verifycate only issues SELECT requests through Supabase's REST API. There is no
write path, so a certificate can never change the data it was built from.
Common questions
- Which Supabase keys does Verifycate need?
- A secret or service key that can read the tables you want to import from. The key is validated, encrypted at rest and never returned by the API.
- Can I import from a private schema?
- Version 1 reads the public schema through Supabase's REST layer. Tables and views in public are listed; other schemas are a later addition. A view in public is the simplest way to expose a curated list today.
- Does this replace uploading a spreadsheet?
- It replaces the export. You still review the mapped rows and validate emails before they are added, so a bad source row cannot quietly become a certificate.
Related
Keep exploring
Start issuing
Ready to connect your first integration?
Start with 300 free credits. No card required.