Skip to content
Anslation

Back-office portal tasks, done on schedule and on the record.

AnsBot automates the back-office jobs that are the same clicks in the same web portal every week: sign in, open a page, update a record, check the confirmation. It repeats them with your sign-in from an encrypted vault or a saved browser session, hourly, daily or weekly or by webhook, and keeps a log, its output and screenshots where it stops.

A portal task, step by step. Set up once.

  1. Save the sign-in

    Put the portal's sign-in details in the bot's vault, or save a signed-in browser profile.

  2. Record the task

    Do it once with the AnsBot Recorder: open the page, update the record, save.

  3. Add checks

    Verify the confirmation text and read the reference number into the output.

  4. Pin what each run uses

    Each schedule names its own version, vault entry, inputs and mode, and each webhook its own version, vault entry and mode.

  5. Schedule it or trigger it

    Hourly, daily or weekly, or by webhook from another system.

  6. Review the runs

    Read each run's log and output; failed runs keep a screenshot and a checkpoint to resume from.

Ways to sign in to a portal. Pick the one that fits.

AnsBot sign-in options
WayHow it worksFits
Vault entryStored encrypted; filled through {{credential_username}} and {{credential_secret}}; masked in logs.Portals with a username and password.
Browser profileA saved signed-in session, stored encrypted, used by one run at a time.Portals that keep you signed in.
Per schedule or webhookEach one names the vault entry its runs use.A test account and a live account side by side.
Permission policyAllows only the portal's domains and asks before stored sign-ins are used, when switched on.Teams that want a check on sign-in use.

Not supported. Check before you start.

It does

  • Runs on public portals you are allowed to automate.
  • Keeps the published version running while a repair is tested.

It does not

  • Answer one-time codes or two-factor prompts.
  • Reach portals on an intranet or a private network.
  • Download reports or attach files.
  • Run on cron expressions.

When the portal changes. What happens next.

  • Fallbacks firstA step tries other saved targets and selectors that worked before.
  • Repairs are testedA proposed repair runs in a shadow test on a copy of the bot.
  • A person publishesNothing changes in the live bot until someone with publish rights approves.

Portal tasks: questions.

Still have a question? Ask us

Can AnsBot sign in to a web portal for me?

Yes, with your own sign-in: details in the bot's vault are stored encrypted and filled through {{credential_username}} and {{credential_secret}}, or a saved browser profile keeps a signed-in session between runs.

Can it handle two-factor sign-in?

Not by itself: there is no one-time-code input. A browser profile can keep a signed-in session between runs for portals that allow it.

Can AnsBot reach our intranet portal?

No. Runs reach public websites only; private and internal addresses are refused.

What happens when the portal's pages change?

The step tries its fallbacks first. A repair is then proposed, tested in a shadow run on a copy of the bot, and published only when someone with publish rights approves it.

Hand AnsBot the weekly portal chores.

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