FAQ
Answers for founders integrating ImportFlow.
Short answers to reduce setup uncertainty before you wire the widget into a real app.
Do I need a real Supabase project to try ImportFlow?
No for the playground. Yes for a real integration. The playground stays browser-local; production widgets require a verified dashboard project.
What is a Project?
A Project represents one connected Supabase app. It stores the Supabase URL and service-role key as an encrypted write-only credential used server-side.
What is an Import Kit?
An Import Kit is a template-specific widget configuration with a destination table, field config, and public embed token.
Is the embed token a secret?
No. It is a public, widget-scoped token. ImportFlow validates it server-side on every widget request, and it never grants dashboard access.
Do failed rows count toward billing?
No. Only inserted rows count toward account usage.
Can I use custom templates?
No. ImportFlow supports CRM Leads, HR Employees, and SaaS Users so the product stays predictable and supportable.
What happens if webhook delivery fails?
The import remains completed or failed according to the lifecycle. The delivery row is marked failed, and owners can retry manually from the dashboard.
Ready for the real setup path?
Start in the dashboard, connect Supabase, create a kit, and copy the exact snippet.