ImportFlowDefine the import
Choose the destination and the fields customers can supply. Set the validation rules and keep generated or system-owned fields under application control.
The integration model
Your app owns the rules. ImportFlow handles the import experience.
Embed the customer-facing workflow and connect it to the context your application already understands. Identity and business authority stay with your app.
Your application
User identity, tenant context, allowed operations and business rules.
ImportFlow
File preparation, mapping, validation, guided corrections, review and import coordination.
Your destination
Database constraints and the recorded outcome of accepted changes.
Three decisions shape the integration.
Connect your application context
Start the flow for an authorized user and workspace. Supply tenant and protected values from your backend rather than from the spreadsheet.
Make the result part of your product
Give customers a review step before confirmation, then account for the recorded outcome. An uploaded file and a completed import are different states.
Less custom import UI. A clearer operational handoff.
Mapping, corrections and import coordination belong to the same customer journey. Keeping them together reduces the separate screens and support explanations your team has to assemble.
Starting with Supabase.
The first integration is focused on Supabase applications and a React frontend. Your engineer connects authorization and destination rules; ImportFlow provides the import workflow around them.
Read the engineering guidesEarly Access
Building a customer import? Let’s talk.
We’re preparing the first public release, starting with Supabase. Early Access is the way to express interest today.