Wire your voice agent into any stack
Dograh is the self-hostable voice agent platform with an open-source workflow builder. If a system can send or receive a web request, it can start a call, feed it live data or catch the result.
Pick the moment, then the destination
Start the call from your system
API Triggera URL that starts a call
Your CRM or backend posts a phone number and context, so the agent opens with the caller's name.
→ Inbound calls can fetch caller details first
Read and write live data
HTTP API toola REST call the agent makes
The agent checks an order or books a slot while the caller is still talking.
→ Write the error path into the prompt
Send the result anywhere
Webhook nodea POST once the call ends
Each finished call posts its outcome to any URL, in a JSON shape you choose.
→ Key every write on workflow_run_id
What each moment looks like in code
curl -X POST https://your-dograh-instance/api/v1/public/agent/{uuid} \ -H "Content-Type: application/json" \ -H "X-API-Key: dg_your_api_key" \ -d '{ "phone_number": "+1415555XXXX", "initial_context": { "customer_name": "Jane", "appointment_date": "March 15" } }'
{ "call_id": "{{workflow_run_id}}", "first_name": "{{initial_context.first_name}}", "rsvp": "{{gathered_context.rsvp}}", "disposition": "{{gathered_context.call_disposition}}", "duration": "{{cost_info.call_duration_seconds}}", "recording_url": "{{recording_url}}", "transcript_url": "{{transcript_url}}" }
curl --get https://api.calendly.com/event_type_available_times \ -H "Authorization: Bearer YOUR_CALENDLY_TOKEN" \ --data-urlencode "event_type=https://api.calendly.com/event_types/YOUR_EVENT_TYPE_ID" \ --data-urlencode "start_time=2026-10-06T13:00:00Z" \ --data-urlencode "end_time=2026-10-07T01:00:00Z"
Point each moment at what you already run
The production URL runs only the published workflow
Slow outside APIs need a short holding line
One agent can carry several Webhook nodes
Built for the stack you already run
No connector to wait for
Anything with an HTTP API or a webhook URL works today.
You own the field mapping
When an app's API changes, you edit your own template.
Lookups next to the agent
Self-host beside your database so mid-call reads stay quick.
One ID joins every event
workflow_run_id links each result to the call that started it.
Open mechanisms vs built-in connectors
| What you get | Dograh | Built-in connectors |
|---|---|---|
| Connects to any app with an HTTP API, no connector needed | ✓ | ✕ |
| You decide which call fields go where, in your own template | ✓ | ✕ |
| Self-host next to your database for quick mid-call lookups | ✓ | ✕ |
| Call data goes only where you point it | ✓ | ✕ |
Learn how it works, step by step
Does Dograh have native CRM or Calendly connectors?+×
No. Your CRM, Calendly and n8n are destinations. You reach them through an HTTP API tool, the API Trigger or a Webhook, like any other system.
How do I start a Dograh call from my own backend?+×
POST a phone_number to the API Trigger URL with your X-API-Key header. Values in initial_context become template variables in the agent's prompts.
What happens if my webhook endpoint is down when a call ends?+×
By default the delivery is logged and not sent again. You can turn on retries with retry_config, and compare workflow_run_id values to spot missing results.
What happens when a tool call fails mid-call?+×
Any 4xx or 5xx response, timeout or connection failure comes back as an error. Write that path into the prompt so the agent offers a callback.
Can I connect n8n or Zapier?+×
Yes. n8n's HTTP Request node can call the API Trigger, and an n8n Webhook node or a Zapier Catch Hook can receive Dograh's Webhook.
Keep the mapping. Ship the agent.
Self-host in one command, or start on Dograh Cloud.
$ curl … start_docker.sh && ./start_docker.sh