How do I generate flows from a repo?
If your codebase already describes user journeys — in end-to-end tests, route files, or docs — you don’t have to author Flows from scratch. AccessLint can read a connected GitHub repository, propose the journeys worth monitoring, and save the ones you pick as draft flows. (No GitHub connection? You can generate flows from a typed list or CSV instead.)
Prerequisites
- The AccessLint GitHub App installed, with at least one active repo (check your repo settings). Email-only workspaces can’t use this feature, since it reads from GitHub.
- A verified domain to attach the generated flows to.
Generate
- Open Flows in your dashboard and click Generate flows.
- Under From your repo, choose the repository to analyze and click Analyze repo.
- Proposed journeys stream in as AccessLint reads your end-to-end tests (Playwright, Cypress, and similar), routes, and docs. Journeys that appear to require sign-in are marked Sign-in required.
If no end-to-end tests are found, AccessLint falls back to inferring journeys from your routes and docs alone — those drafts are marked accordingly, so review them extra closely.
Generation is limited per day; if you hit the limit, try again tomorrow.
Review and save
- Pick the journeys worth monitoring — skip the rest.
- Choose the domain to attach them to.
- Click Save selected as drafts.
Each saved journey becomes a draft flow. Like any flow, a draft doesn’t monitor anything until you review its steps, run a dry run, and approve it — see How do I author a flow? Generated steps are a head start, not ground truth: read them, fix anything that doesn’t match your site, and add variables for any credentials a sign-in journey needs.
Your latest analysis is saved, so you can leave the page and come back to the same results — journeys you’ve already saved stay marked Added.