guide · flows

create guided flows

flows let the agent take the first move. instead of waiting for a user to ask for help, define the steps — the agent walks them through automatically, triggered by the right moment.

  1. 01

    open the flow editor

    go to your aside dashboard, select your workspace, then click the flows tab. you'll see a list of all flows — active, draft, and archived. if this is your first time, it'll be empty.

    dashboard path

    dashboard → your workspace → flows

  2. 02

    create a flow

    click new flow and give it a descriptive name. names are internal only — users never see them. use something that makes the intent obvious, like new user onboarding or billing upgrade prompt . you can also add an internal note to remind yourself why you built it.

  3. 03

    choose a trigger

    the trigger decides when the flow runs. pick the one that matches your intent.

    first_visit

    fires automatically for new users on their first session. perfect for onboarding.

    url_match

    fires when the user's active tab url matches a pattern you specify. useful for feature-specific nudges.

    manual

    fires only when you call the aside api with a specific flow id. use this when your app controls the timing.

  4. 04

    add steps

    each step has three fields. the agent reads instruction aloud. detection is how aside knows the user completed this step (e.g. page:/settings means "navigated to /settings"). when timeout seconds pass without detection, the agent re-prompts automatically.

    json

    {
      "instruction": "let's set up your first workspace. click the settings icon in the top-right.",
      "detection": "page:/settings",
      "timeout": 30
    }

    instruction

    what the agent says aloud. keep it one action at a time.

    detection

    a page: or element: rule that marks the step complete.

    timeout

    seconds before the agent re-prompts. 20–40 is a good default.

  5. 05

    enable the flow

    new flows start in draft mode. when you're ready, toggle the flow to active. the next session that matches your trigger will run it immediately — no deploy required. you can pause or archive a flow at any time without affecting active sessions already in progress.

    toggle to active → changes take effect on next session

  6. 06

    test it

    open an incognito tab (for first_visit triggers) or navigate to the matching url (for url_match ) and click the aside widget. the agent should greet you and begin guiding through step 1 of your flow automatically. if it doesn't fire, check that the flow is active and the trigger condition is met.

    01

    open an incognito tab

    02

    click the widget

    03

    agent begins step 1

what's next