Replay and automation
Replayable browser workflows
Every Autodocs recording is saved as a browser workflow that an Autobot replays step by step, on demand, on a schedule or from a trigger.
THE PROBLEM
Documenting a chore doesn’t make it go away
Screenshot-guide tools stop at the guide; someone still has to do the task every week. With Autodocs the recording is also a browser workflow, so the same capture can do the task for you.
Each recording is saved as a browser workflow that replays the same clicks, typing and choices in an Autobot’s browser, on demand or on a schedule.
How it works
How does replayable browser workflows work in Autodocs?
- 1
Record once
The recording is saved as a workflow under Workflows in Autodocs and in an Autobot’s Workflows tab.
- 2
Run it in an Autobot’s browser
Pick an Autobot and run the workflow from its Workflows tab, or just ask it in chat to run “Refund a damaged order”.
- 3
Watch or walk away
The Autobot’s live browser shows the run. You can watch, take over or stop it; the browser stays open when stopped.
- 4
Put it on a schedule or a trigger
Autobots run on schedules and triggers too, each run optionally in a fresh browser of its own, with replies by email or Slack.
- 5
Get every step’s result
Each step reports passed, healed or failed, and steps after a failure read as skipped.
Options and settings
Every option, in one table
| Action | What it does |
|---|---|
| Run | Replays the workflow in an Autobot’s browser, as you, with your saved sign-ins for that Autobot. |
| Stop | Ends the run where it is; the browser stays open. |
| Rename | Renames the workflow. Names pick a workflow when you ask an Autobot to run one. |
| Delete | Deletes the workflow for good. The doc written from it stays. |
| Last run | Each workflow shows whether its last run passed or failed, and when. |
| CLI | `autessa browser-workflows list | steps | run | run-status | delete`. |
Who can do what
Permissions
| Who | Can |
|---|---|
| The person who recorded a workflow | Sees its steps, renames it, replays it and deletes it. Workflows are personal. |
| An Autobot | Runs your workflows in its own browser when you ask, on a schedule or from a trigger. |
AI assist
Where AI helps
An Autobot can also record a workflow itself: you ask it to automate a task, it does the task step by step in its browser while recording, then saves it for you.
Connects to
How it fits with the rest of Autodocs and Autessa
FAQ
Replayable browser workflows: questions
Can I replay a recorded browser task automatically?
Yes. Every Autodocs recording is a workflow that an Autobot replays on demand, on a schedule or from a trigger.
Who can run my workflows?
Workflows are yours: they belong to the person who recorded them and run as you, in an Autobot’s browser.
What happens if a step fails?
The run stops there and reports it; every later step reads as skipped, so you see exactly how far it got.
Do I need to write code?
No. You record by doing the task. Developers can also run workflows from the Autessa CLI.
Try replayable browser workflows on a task you do every week.
Record it once in Autodocs. You get the guide for your team and the workflow for next time.
No extension to install · nothing is published until you publish it
100% customizable, code and all
Make Autessa Autodocs fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours