Developers build
Record or draft a bot and edit its steps.
AnsBot gives each bot its own team with five roles, keeps every change in a numbered version that can go through review, and lets you mark the steps that must wait for a person. Runs you start can use the test, staging or production environments you define; every run masks values marked secret and keeps a log, its output and screenshots where it stops.
| Control | What it does |
|---|---|
| Team roles | Owner, staff, developer, operator and reviewer per bot; each member allowed or refused training, running, publishing and managing the team. |
| Versions | Every change is a numbered version, draft, published or retired; compare two and roll back. |
| Reviews | A version under review, or rejected, cannot be published; each decision is kept. |
| Approval steps | Marked steps stop the run until a person approves or rejects them. |
| Permission policy | Allowed actions and domains per bot, with approval before submit-like clicks, uploads, stored sign-ins and moves to another domain. |
| Environments | Test, staging and production presets for version, inputs, sign-in, browser, queue and attempts. |
| Quality gate | Scores whether a bot is ready; runs started from the console and client portal runs must pass it. |
| Masking | Values marked secret become [redacted] in logs, outputs, errors and callbacks. |
| Retries | Failed attempts retry with growing gaps, then wait in a dead-letter queue for an operator. |
| Callback signing | Results posted to your systems carry an HMAC-SHA256 signature when the endpoint has a signing key. |
Record or draft a bot and edit its steps.
Approve or reject a version before it is published.
The owner, or a member with the publish right, publishes the version.
Start, pause and retry runs, and answer approval requests.
Manage the team and the client billing.
Start runs and export results from a signed portal link.
Still have a question? Ask us
The bot's owner, and team members given the publish right. Roles per bot are owner, staff, developer, operator and reviewer, and each member can be allowed or refused training, running, publishing and managing the team.
Yes. Send a version for review and it cannot be published while the review is pending or after it is rejected; every decision stays in the version's review history.
In the bot's vault, stored encrypted with an application key and shown only as a masked preview. A run fills them through {{credential_username}} and {{credential_secret}}, and they appear as [redacted] in logs, outputs and callbacks.
No. Runs reach public websites only, from Anslation's servers, and private and internal addresses are refused; AnsBot's workers cannot be hosted in your own network.
Yes, per bot: add people to a bot's team with a role and allow or refuse each right. Someone outside the team, without AnsBot administrator access, cannot open that bot.
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