Workflows and reports
Do it once. Run it again.
When the agent finishes a task the way you wanted, save it as a workflow. Next week, give it new inputs and it follows the same steps on the pages as they are then.
- Save what worked
- A finished task that was checked step by step can be kept as a workflow, with the parts that change marked as inputs.
- Run it with new inputs
- A different supplier, a different month, a different list of pages. The steps repeat; the content is read fresh each time.
- One case at a time
- Give it a list and it works through each item, reporting a result for every one rather than a single pass or fail.
Longer tasks
Work that takes more than a minute.
Some jobs have conditions, loops and smaller jobs inside them. OwnWeb plans these as steps it can check, and keeps a record you can read afterwards.
What you get at the end
- A history of what was done, in order, with what the agent saw at each step.
- A report in Markdown or JSON, saved to a folder you approved.
- A receipt for each outcome, so “done” means something was verified, not just attempted.
- The option to continue a finished task: “now email me that report”.
Sending a report by email needs a mail connection you have set up, and your approval.
In your hands
Stop, pause, set a limit.
A long task should never feel like something you started and cannot control.
- Stop or pause
- Stop a task at any moment. Pause one and pick it up later.
- A budget
- Give a task a limit. If it needs more, it stops and asks before going on.
- It survives a restart
- Close the browser mid-task and it resumes from where it was, without repeating steps that already had an effect.
- Attended or unattended
- Watch a task work in its own window, or let it run in the background inside the permissions you granted.
- Approvals still apply
- A saved workflow gets no extra rights. Steps that send, submit or delete still need an approval you gave.
- Recurring tasksComing
- Run a workflow on a schedule, with a standing approval you can withdraw at any time.
Replay works for tasks whose steps were verified when they first ran, not for every request typed into the chat. Websites change, and a workflow that cannot find what it expects stops and tells you.
Next