Refund a damaged order
Use this when a customer reports a damaged item. It takes about a minute in the payments portal.
4. Click Refund.
Autessa Autodocs
Autessa Autodocs is a step-by-step guide generator and browser workflow recorder. Do a task once in a browser inside Autessa and you get a how-to guide with a highlighted screenshot for every step, plus a self-healing workflow that replays the task whenever you need it. Each replay refreshes the guide’s screenshots, so your process documentation stays current on its own. It is free with every Autessa account, for unlimited users; you pay only for AI tasks. It works out of the box, and you shape it to how your company works in Autessa.
↳ FOR PEOPLE · THE GUIDE
↳ FOR THE BROWSER · THE WORKFLOW
FREE · UNLIMITED USERS
Everyone on your team can record guides and workflows, with no per-seat fees. Autodocs is free with every Autessa account. You pay only for AI tasks.
Let the people who know each job record it. Nobody needs a license to write a guide.
AI tasks, such as the AI writing your guide, are the only thing you pay for.
One recording, two outputs
Screenshot-guide tools stop at the page people read. Record-and-replay tools give you code someone has to maintain. In Autodocs the guide and the workflow are the same recording, so they never drift apart.
FOR PEOPLE
A title, an introduction and one instruction per step, buttons named in bold, with a screenshot that highlights exactly what to click. Edit it in Markdown, publish it to your knowledge base, and your chatbots answer from it.
FOR THE BROWSER
The same clicks, typing and choices, replayed by an Autobot on demand, on a schedule or from a trigger. If the page changed, the browser’s AI finds the element by meaning and the step reads as healed.
How it works
The guide takes as long as the task itself.
A real browser opens inside Autessa. No extension, no desktop app.
Click, type, scroll and choose like you always do. Each step appears as you go, in plain words.
Autodocs saves the workflow and writes the guide, a highlighted screenshot for every step.
Publish the guide to your knowledge base. Replay the workflow whenever the task comes around.
What makes it different
Everything a process documentation tool should do, plus the things that only happen when the guide and the automation are one.
Self-healing replay
Self-updating screenshots
Docs become automation
An agent for every doc
AI documents AI
Passwords stay out
Product tour
Autodocs is small on purpose: a recorder, your docs, your workflows. Here is all of it.
SCREEN 01
Docs on the left, marked Draft or Published, and your recorded workflows below them with Write doc or Open doc beside each. The open doc has Edit, Create agent or Open agent, Create workflow, Publish and Delete, and a link to its folder in Drive.
SCREEN 02
A live browser with its own address bar on the left; every recorded step, with its pause, on the right. Name it, choose the replay pace, then Finish or Discard.
SCREEN 03
Its steps as recorded, how it replays, when it last ran and whether that run passed. Rename it, write its doc or delete it; deleting keeps the doc.
SCREEN 04
Markdown on one side, the finished guide on the other, screenshots included.
SCREEN 05
Drafts and Knowledge base folders in your company’s Autodocs Drive; each doc a folder of article, pictures and details.
SCREEN 06
Everything in Autodocs, and every workflow, from the Autessa CLI.
AI how-to guide generator
Knowledge base
Record and replay browser automation
Everything in Autodocs
Each chapter has its own page, and every feature has a page of its own with how it works, every option and who can do what.
CHAPTER 1
Autodocs records a task while you do it once in a real browser inside Autessa, capturing every click, keystroke, choice and pause as a plain-language step.
CHAPTER 2
Autodocs writes the how-to guide for you: a title, an introduction and one clear instruction per step, each with a screenshot that highlights what to click.
CHAPTER 3
Every Autodocs recording is also a self-healing browser workflow that an Autobot can replay whenever you ask, on a schedule or when something happens.
CHAPTER 4
Autodocs keeps guides current by re-shooting their screenshots every time the workflow runs and flagging the steps where the site has changed.
CHAPTER 5
In Autodocs a document and an automation are the same thing seen two ways: docs become workflows and agents, and the work Autobots do becomes docs.
Use cases
Anyone who does a task in a web app that someone else will need to do, or that should simply happen on its own.
SOPs for every back-office task in a web app, kept current by the runs that do the task.
Step-by-step answers for agents and customers, found by your support chatbot.
How-tos for account setup and admin consoles, with workflows that repeat the clicks.
New-hire guides recorded by the people who know the job, in minutes.
No-code checks that sign-in and checkout still work, with every step’s result.
Monthly downloads and portal chores documented once and replayed on a schedule.
Works with
Docs live in Autessa Drive. Workflows run in Autessa Autobots. Chatbots read the knowledge base. And it all works from the Autessa CLI. Because Autodocs records in a real browser, it works with any website you can sign in to.
Security
Yes. Autodocs is designed so the people reading a guide never see a secret, and nothing leaves draft until a person publishes it.
Typed secrets never appear in visible steps or guides; runs ask for passwords and codes in the moment.
Saved workflow steps are encrypted before they are stored.
Workflows belong to the person who recorded them and run as that person.
Nothing is published until a person publishes it. Delete goes to the Drive trash.
Self-updating documentation
After each run, a guide lists the steps where the site drifted from the recording: healed, failed or not reached. Every other step is confirmed as still matching. Your team reviews the few steps that changed, not every page.
Website change notes →The essentials, done well
Autodocs includes a browser task recorder: press Record a workflow, do the task once in the browser that opens, and every action is captured as a plain-language step.
Read the page →2Every step in an Autodocs guide has its own screenshot with a highlight around the exact button, link or field that was used.
Read the page →3Autodocs guides are edited in Markdown with a live side-by-side preview that shows every screenshot in place.
Read the page →4Autodocs guides stay drafts until you publish; publishing moves them into the knowledge base, where Drive search and chatbots that use it find them.
Read the page →5Every Autodocs guide is a folder in your company’s Autodocs Drive, so Drive search, sharing, versions and the trash all work on it.
Read the page →6Autodocs has a command line: `autessa autodocs` generates, edits, publishes and converts docs, and `autessa browser-workflows` lists and runs workflows.
Read the page →Compare
Autodocs does what screenshot-guide tools and browser automation each do, from one recording. See how it stacks up.
FAQ
Autessa Autodocs is a process documentation tool and browser workflow recorder. You do a task once in a browser inside Autessa, and you get two things back: a step-by-step how-to guide with a highlighted screenshot for every step, and a browser workflow that replays the task whenever you need it.
Yes. Autessa Autodocs is free with every Autessa account, for unlimited users, with no per-seat fees. You pay only for AI tasks.
Yes. Press Record a workflow, do the task once and your first guide and workflow are ready. From there you shape Autodocs to how your company works in Autessa: edit the guides, publish them to your knowledge base, put workflows on a schedule, and give a doc its own agent.
It writes the guide from your recording. When you save, a model turns the recorded steps into a title, a short introduction and one plain-language instruction per step, naming buttons and fields in bold, and Autodocs draws a highlight around the element you used on each step’s screenshot. The guide is a draft you can edit before publishing.
No. The recorder is a live browser that runs in the cloud and shows inside Autessa, with its own address bar. You click, type and scroll in it right in the page.
They update. Every time the workflow runs, Autodocs re-shoots each step and refreshes the screenshots in every doc written from it. The doc then lists any step where the site no longer matched the recording, marked healed, failed or not reached, so you know what to review. An Autessa agent can also email the guide’s owner the steps that need a look, when you ask it to.
Self-healing replay means a small page change does not break the run. Each step first uses the element it was recorded on; if that element is gone or moved, the browser’s AI finds it by what it means, such as the Save button, and the step is reported as healed.
No. The guide is written never to include a password, and typed secrets never appear in the steps people see. When a replay reaches a password or one-time code field, it can ask you for it and type it straight into the field without storing or logging it.
Yes, in two ways. Create workflow turns a doc’s numbered steps into a browser workflow that the browser’s AI carries out one instruction at a time, and Create agent gives a doc its own Autobot that re-runs the recorded steps in its own browser.
In your company’s Autodocs Drive. Each guide is a folder holding the article, its step pictures and its details. Drafts sit in a Drafts folder; published guides move into the Knowledge base folder, where Drive search and chatbots that use the Autodocs Drive find them.
Yes. Workflows run in an Autessa Autobot’s browser, so you can ask an Autobot to run one now, or give it a schedule or a trigger. Each scheduled run can get a fresh browser of its own, and replies can reach you by email or Slack.
People whose role can use agents. Workflows belong to the person who recorded them; the docs live in the company’s Autodocs Drive, where Drive sharing decides who sees them.
Yes. `autessa autodocs` lists, opens, generates, edits, publishes, converts and deletes docs, and `autessa browser-workflows` lists workflows, reads their steps, runs one in an Autobot’s browser and follows its progress.
Pick the task you explain most often and do it once. Autodocs works from the first recording; publish the guide, schedule the workflow and shape the rest to how your company works.
No extension to install · nothing is published until you publish it
100% customizable, code and all
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