Dialora Webhooks Integration Guide: Automating Outbound Calls
What Are Webhooks and Why Do You Need Them?
Think of webhooks as automatic notifications between different software systems. When something happens in one app (like a form submission on your website), a webhook instantly tells another app (like Dialora) to take action. In the context of Dialora, webhooks enable you to trigger outbound calls automatically whenever specific events occur in your business processes. No manual intervention required.
Common Use Cases
- Lead Generation: Automatically call new leads who fill out contact forms.
- Content Downloads: Follow up with prospects who download gated content.
- Event Registrations: Confirm attendance with registered participants.
- Support Requests: Initiate callback requests from your support system.
- Sales Pipeline: Trigger calls when leads reach specific stages.
Webhooks or the Calls API?
You have two ways to start a call from your own systems, and they suit different setups.
| Webhooks | Calls API | |
|---|---|---|
| Best for | No-code tools — Zapier, Make.com, n8n, form builders | Your own backend, CRM, or scripts |
| You send | A payload to a Dialora webhook URL | An authenticated POST to /api/v1/calls |
| Auth | The webhook URL itself | An API key with scoped permissions |
| Results | Delivered to your endpoint | Delivered to your webhook, signed so you can verify it came from us |
If you’re wiring Dialora into an automation platform, stay on this page. If you’re writing code, use the Calls API below.
Calls API
Start phone calls programmatically with a single request — no dashboard needed.
- Launch a call with your agent, a destination number, and per-call variables
- Attach your own metadata to a call and get it echoed back to you
- Receive a completion webhook with the call outcome and any data your agent extracted, signed so you can verify the sender
See the API Reference for every endpoint, request shape, and response schema.
API Keys and Scopes
Create and manage API keys from your profile under API Keys. Each key carries exactly the permissions you grant it — least privilege by default — and you can revoke or re-scope a key at any time.
Scopes available on account keys:
| Scope | What it allows |
|---|---|
calls:read | Read call and conversation data |
calls:write | Initiate and manage outbound calls |
Agency (tenant-level) keys can additionally be granted users:read, users:write, plans:read, subscriptions:read, and subscriptions:write.
An API key is shown once, at creation. Store it in your secret manager, never in client-side code or a shared document. If a key may have leaked, revoke it — creating a replacement takes seconds.
The same API keys authenticate the Dialora MCP Server, so a key’s scopes also determine what Claude, ChatGPT, or Cursor can do on your behalf.