Flow Creator

How it works

From repository to monitored flow

The same journey goes from description to diagram, from diagram to run, and from one run to a check that runs on its own.

  1. Create your organization and a project

    Sign in with the account you were invited with. Then name your organization and start a project. Invite the people you work with as viewers, editors or owners.

  2. Connect your repositories

    Add the GitHub repositories of your API and, if you have one, your React frontend. Flow Creator reads endpoints, records, roles and pages from them. A scan takes seconds and can run again whenever the code changes.

  3. Describe a journey, or take a tour

    Write the journey the way you would explain it to a colleague. Flow Creator draws it with a lane per role, and you can edit every step. Or pick a role and get a tour of everything it may do.

    “A company admin logs in. The company admin sees the users and can create a user. An employee logs in. The employee sees the products and can order a product and update their order.”

    1. Company AdminPOST /realms/portal/protocol/openid-connect/token
    2. Company AdminGET /api/users
    3. Company AdminPOST /api/users
    4. EmployeePOST /realms/portal/protocol/openid-connect/token
    5. EmployeeGET /api/products
    6. EmployeePOST /api/orders
    7. EmployeePATCH /api/orders/:id

  4. Run it against the mock

    Press “Run flow”. Each role signs in to the mock, steps call their endpoints with ids from earlier answers, and the canvas marks every step as it passes or fails. Add checks to a step to say what the answer must contain.

  5. Add a live environment

    Give your test or acceptance environment an address and credentials per role, and the same flow runs there. Writes stay off until you allow them.

  6. Monitor, audit and load test

    Switch on monitoring and choose where alerts go. Run the access audit to see what each role can reach that it shouldn’t, and load test the steps that matter under traffic. Call the deploy hook from CI to check every deploy.

Start with one journey

Most teams start with sign-in and the one action their users do most.

Log in See how it works