Log in

Use case

The same eleven portals every morning, by hand.

Sign in, read a number, copy it somewhere, sign in to the next one. It is the work that never gets automated, because every portal is a little different and none of them has an API. Describe the round once and the agent runs it, on a schedule or when you ask.

Run the free check
Download and run one real task
Workflow · morning-claims

morning-claims

Recorded once. Replayed with the slots filled in.

9 steps
portalsince
  1. 1open_page → portal login ⟨portal⟩
  2. 2credential_fill → sign-in form
  3. 3wait_for → "Open claims"
  4. 4click → "Open claims"
  5. 5fill_form → date filter ⟨since⟩
  6. 6click → "Apply"
  7. 7read_text → results tablereads
  8. 8click → "Export CSV"
  9. 9download_file → claims.csv

Eleven portals, one recipe each. The password is not in here: the daemon looks it up at replay.

  • Recorded once, replayed after that

    A recipe remembers roles and names, not element ids, and searches against a fresh page map when it runs. A stored id would address whatever inherited it tomorrow.

  • Each portal keeps its own profile

    Eleven logins, eleven identities, no mix-ups and no shared session between two of them.

  • You see what it did

    Every step carries its result and a still image, and secrets are blacked out in the picture instead of the picture being dropped.