Skip to content
Anslation

AnsBot is browser automation with human approval and run evidence.

AnsBot repeats a web task in a browser on Anslation's servers: it opens the page, fills the fields, clicks, checks the result and reads values back. You record or describe the task, review the steps and mark the ones that wait for a person; every run keeps a step log, its output and screenshots where it stops.

Already a customer? Open the console

How a run works. Five steps from a manual task to a repeatable one.

  1. Record or describe the task

    Do it once in your browser with the AnsBot Recorder, or give a start URL and a goal and let AnsBot draft the steps.

  2. Review the steps

    Check what each step opens, fills, clicks, checks or reads. Drafts are saved as drafts and never run on their own.

  3. Choose inputs and approvals

    Turn values into {{inputs}}, keep sign-ins in the vault and mark the steps that must wait for a person.

  4. Start runs your way

    By hand, on a schedule, by webhook, from a CSV or JSON batch, from a client portal, or from Ansi after approval.

  5. Check the evidence

    Read the step log, the output and the screenshots, and resume a failed run from the step that failed.

What AnsBot gives your team. Each one links to how it works.

  • Human approval

    Steps that wait for a person, and a permission policy for risky actions.

  • Run evidence

    A log of every step, the values read, screenshots where a run stops, private traces of failures.

  • Reviewed repairs

    Fixes proposed when a page changes, tested in a shadow run and published only on approval.

  • Roles and versions

    Five team roles per bot, numbered versions, and reviews that hold back a release.

  • Webhooks and callbacks

    Start runs from other systems and get each result back, signed when you add a signing key.

  • Client portal

    Clients start runs, see results and export them from a signed link.

What AnsBot does, and what it does not.

It does

  • Repeats the steps you reviewed, the same way each time.
  • Fills forms, clicks, picks options, checks text and reads values back on public websites.
  • Stops at the steps you mark until a person approves.
  • Retries failed attempts with growing gaps, then parks them for an operator.
  • Masks values marked secret in step logs, outputs, errors, approvals, exports and callbacks.

It does not

  • Solve CAPTCHAs, or get around sign-ins, paywalls or bot checks.
  • Reach sites on a private network, an intranet or localhost.
  • Upload or download files, or run a step only when a condition holds.
  • Run inside your own Chrome: runs use a headless browser on Anslation's servers.
  • Decide on its own what to click: no model chooses actions during a run.

Six ways to start a run. All of them go through one run service.

Ways to start an AnsBot run
WayHow it startsGood for
From the consoleBy hand, in test or production mode.Trying a bot and one-off runs.
On a scheduleHourly, daily or weekly, at an interval you set.Routine portal and reporting tasks.
By webhookAn HTTPS POST with the endpoint's own token; the JSON body becomes the inputs.Release checks and other systems.
From a data batchCSV or JSON rows, up to 1,000 per batch, one run per row.Data entry from a spreadsheet.
From a client portalYour client starts it from a signed link you shared.Agencies delivering work to clients.
From AnsiAnslation's assistant asks, and an AnsBot admin approves first.Starting a run from a conversation.

Every way in creates the run through the same run service.

Questions about AnsBot. Short answers.

Still have a question? Ask us

What is AnsBot?

AnsBot is Anslation's browser automation for business web tasks. You record or describe a task, review the steps, and AnsBot repeats them in a headless browser on Anslation's servers, stopping for a person at the steps you mark and keeping a log of each step, its output and screenshots wherever a run stops.

Is AnsBot an AI agent?

No. A run follows the steps you reviewed, the same way each time, and no model chooses what to click while it runs. AI only drafts steps from your description and suggests repairs after a step fails, and only where the Anslation model gateway is enabled; otherwise built-in rules do both.

Can a person approve a step before AnsBot does it?

Yes. Mark a step as needing approval and the run stops before it, with a screenshot of the page, until someone approves or rejects it in the inbox. Once approved, the run starts again at that step, reopening the page it was on; a rejected run is cancelled.

Can AnsBot work on any website?

No. Use it on public websites you own or are allowed to automate. Runs cannot reach private or internal addresses, and AnsBot does not solve CAPTCHAs or get around sign-ins; it signs in with your own details from the bot's vault.

What does a run leave behind?

A log entry for every step with its status, the element it used and a message; the values its extract steps read; screenshots at screenshot steps, approval waits, operator pauses and failed steps; and, for a failed attempt, a private browser trace that expires.

How do I get AnsBot?

Ask for access through the contact form. AnsBot is turned on per account and has no self-serve sign-up or published price; existing customers open it from the Anslation console.

Bring a web task. Ask for AnsBot access.

Tell us the web task and the site it runs on. We read every request and reply by email.

Office hours: Monday to Saturday, 10:00–18:00 IST+91 74158 85838