How do I generate flows from a list of journeys?
If you can list your product’s key journeys — sign in and change a setting, search and open a result — AccessLint can draft Flows from the whole list in one batch, instead of you authoring each flow one at a time. Unlike generating from a repo, this works in any workspace, including email-only ones — no GitHub connection required.
You’ll need a verified domain to attach the generated flows to.
Generate
- Open Flows in your dashboard and click Generate flows.
- Under From a list of journeys, describe each journey in plain language, one per row — for example Sign in with email and password, then open account settings. Click Add another journey for more rows, up to 20 per batch.
- Click Generate flows. Proposed flows stream in as AccessLint drafts steps for each row. Journeys that appear to require sign-in are marked Sign-in required.
Generation is limited per day, and each row counts as one generation. If you hit the limit, try again tomorrow.
Import from a CSV instead
If the journeys already live in a spreadsheet — a QA test-case sheet, a Jira or backlog export, a story-map dump — click Import from CSV and choose the file (up to 1 MB). AccessLint maps it to journey rows automatically:
- A first row naming columns like Steps, Description, or Test case is treated as a header.
- If an ID-like column (ID, Case, Scenario…) repeats across consecutive rows, those rows are grouped into one journey — the QA-sheet shape, where each row is a step.
- Otherwise each row becomes its own journey — the backlog-export shape.
Importing generates nothing by itself. The parsed journeys are appended after anything you’ve already typed, so review the rows, edit or delete any the mapping got wrong, then click Generate flows. If the merged list exceeds 20 rows, only the first 20 are kept and a notice tells you how many were left off.
Review and save
- Under Review and save, check the journeys worth monitoring — skip the rest. You can edit each flow name before saving.
- Choose the domain to attach them to and click Save selected as drafts.
Saved flows are drafts: nothing runs against your site yet. Open each one in the editor, review the steps, add variables for any login secrets, then run and approve a dry run to start monitoring.