Platform · Integrations
Your stack, reachable mid-call.
It books the appointment, updates the record, raises the ticket — while the caller is still on the line. And it's the same machinery the flow engine runs: api-call nodes that template, retry and assert; secrets resolved per organization and redacted on the way back; webhooks with a delivery ledger; and the REST API underneath the dashboard.
The integration surface
- API-CALL NODE
A REST call as a flow step
GET to DELETE with templated URL, headers and body; a per-node timeout; transient failures — 429 and 5xx — retried with exponential backoff from 250ms to a 2-second cap. Outcome ports route strictly, so a failure can never slip down the success path.
- SUCCESSWHEN
It never says “booked” unless it really booked
It checks the real answer from your system — not just that the line connected. Assert on the response body, and the success port is taken only when the status and your assertion both pass, as the self-hosted flow engine enforces; an API that answers HTTP 200 with ok:false is handled as what it is: an error.
- SECRETS-VAULT
Credentials that never touch a prompt
{{secrets.NAME}} resolves per organization, and only inside api-call nodes — everywhere else the reference is stripped, so no secret name or value can reach a prompt or a transcript. Unresolvable references fail closed, and resolved values are redacted from any stored response.
- DELIVERY-LEDGER
Webhooks with receipts
Every webhook delivery is logged — event type, payload, response status and body, duration and attempt number — indexed per organization, per agent and per event, with failures queryable on their own.
- PLATFORM-API
The API under the dashboard
Agents, flows, knowledge bases, calls, analytics, phone numbers and organization secrets are managed over authenticated REST routes with per-org API keys. The dashboard is a client of the same surface you get.
Spec sheet — as enforced in code
- 429 · 5xx
Retryable failures
- 250ms → 2s cap
Retry backoff
- api-call nodes only
Secret resolution scope
- secrets redacted
Stored responses
- SSRF-guarded
Outbound URLs
Retry, redaction and guard behaviour describe the api-call executor as shipped — other 4xx statuses are treated as caller errors and never retried.
The platform
The rest of the platform
- Voice engineArabic replies at human speed — no awkward pause.
- Flow builderDraw your call, publish it yourself.
- Knowledge baseAnswers from your documents — or honestly declines.
- AnalyticsEvery call: its transcript, its cost, its outcome.
- TelephonyYour numbers answered day and night — recorded only with consent.