Connect AnsBot to the systems around it.
Any system that can send an HTTPS POST can start an AnsBot run: each webhook endpoint has its own token, and the request's JSON becomes the run's inputs. When the run ends, AnsBot can post the result back to your endpoint, signed with HMAC-SHA256 when you set a signing key.
Ways in and out. What each one does.
| Integration | Direction | What it does |
|---|---|---|
| Webhook trigger | In | An HTTPS POST with the endpoint's token queues a run; the JSON body becomes its inputs. |
| Run callbacks | Out | AnsBot posts each run's result to your endpoint, signed with HMAC-SHA256 when it has a signing key. |
| Data batches | In | CSV or JSON rows, up to 1,000 per batch, one run per row. |
| Client portal | In and out | Clients start runs and export results from a signed link. |
| Ansi | In | Anslation's assistant reads bots and runs, and drafts, runs or retrains a bot once an AnsBot admin approves. |
Start a run from another system. Five steps.
Create a webhook endpoint
Pick the bot, version and mode; copy the token, which is shown when you create or rotate it.
Send a POST
Call the endpoint's address with the token as a Bearer header and the inputs as JSON.
AnsBot queues the run
The response returns the queued run.
Receive the callback
When the run ends, your endpoint gets its result and status.
Check the signature
Compute an HMAC-SHA256 of the raw body with the endpoint's signing key and compare it with the X-Ansbot-Signature header.
Not available. And what to use instead.
In place today
- Retries failed callback deliveries with growing gaps.
- Redacts values marked secret in callbacks.
Not offered
- Ready-made connectors for other apps: use their webhook or HTTP request step.
- Access keys for scripts: outside systems start runs through webhook tokens.
- Upload files into a run, or download files from a site.
What a callback carries. Read it before you trust it.
- Event and statusThe event name (run.failed, run.completed or run.extracted_data) and the run's status, succeeded or failed.
- The runIts id, bot, version, mode, how it started, summary, error, duration, output and completion time.
- The signatureX-Ansbot-Signature: sha256= followed by the HMAC of the body, when the endpoint has a signing key.
- Your headersCustom headers you add to the endpoint.
- Public targets onlyCallbacks go to public addresses, checked again at every redirect.
Integration questions, answered.
Still have a question? Ask us
Can I start AnsBot from my CI pipeline or another tool?
Yes. Create a webhook endpoint for the bot and send an HTTPS POST with its token; the JSON body becomes the run's inputs and the response returns the queued run.
How do I verify an AnsBot callback?
Compute an HMAC-SHA256 of the raw request body with the endpoint's signing key and compare it with the X-Ansbot-Signature header, which reads sha256= followed by the hex digest.
Are there ready-made connectors for other apps?
No. Use the other app's webhook or HTTP request step to start runs, and an AnsBot callback to send results back.
Can Ansi run my bots?
Yes, with approval: Ansi can read your bots and runs, and draft, run or retrain a bot once an AnsBot admin approves the action. It never publishes a version.
What happens if my callback endpoint is down?
The worker retries the delivery with growing gaps between attempts, up to a set number of attempts.
Connect your systems to your bots.
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