DigitalCallers

Integrations · Automation & Developer

n8n + AI calling

Two-way

Self-hosted automation for teams that want the data on their own servers.

Leads flow in and call results flow back out, both directions wired.

⛓ StepsNever skipped
✨ Off-scriptAI answers
app.digitalcallers.com/agents/29/script

Agent script · guided engine · step 3 of 6

✓Introduce and confirm it's the right person
✓Why we're calling — the form they filled
3Present the programme and ask for the consult
4Handle price / timing objections
5Book the slot
6Confirm and send on WhatsApp
◦ Customer asked something off-script
“Kaun doctor hai, aur fees kitni?”
AI answers from your facts: “Consult MBBS doctor karte hain; fees free consult ke baad batayi jaati hai.” → then step 3's exact line, unchanged.

The agent follows your script step by step, and answers whatever the customer asks in between.

Every business has one workflow that no product supports — the routing rule, the internal tool, the legacy system. That is usually where an integration project dies.

Connecting n8n to DigitalCallers gives you the raw event with a signed, retried, dead-lettered webhook, so you can build exactly the flow you need without waiting for us to ship it. The AI agent speaks Hindi, English and ten other Indian languages, switches between them the way your customers actually talk, and works every hour your calling window allows.

This connects in both directions: records flow in from n8n to start calls, and finished call results flow back out to it.

What teams automate with n8n

Build the flow we haven't thought of

The full call payload — outcome, transcript link, recording, custom fields — is yours to route however your business actually works.

No integration tax

Nothing to buy per connection. If the destination speaks HTTP, it is reachable today.

Delivery you can trust

HMAC-signed, retried with backoff, and dead-lettered with a replay button if your endpoint has a bad hour. Nothing is silently dropped.

Test before you trust it

Fire a sample payload from the dashboard and see the exact JSON your endpoint will receive, before a single real call runs.

What data moves, and which way

From n8n into DigitalCallers

Name, phone number, and whatever else the record carries — campaign, source, product of interest, form answers, order details. Custom fields arrive intact and the agent can use them in the conversation, so the call opens with context instead of “may I know your requirement”.

From DigitalCallers back into n8n

Call outcome and disposition, a written summary of what was said, the customer's intent level, every objection raised and whether it was answered, the quality score, call duration, the next scheduled step, and signed links to the recording and full transcript.

Every client's data is separated at the account level, transcripts are PII-redacted at rest, and numbers are DND-scrubbed before dialling — the same rules apply no matter which app the record came from.

Setting it up

  1. Copy your lead webhook URL: https://app.digitalcallers.com/api/integrations/webhook/<generate-in-Settings>
  2. In n8n, add that URL as an outgoing webhook / POST destination.
  3. Send one test submission — it appears in Contacts within seconds, tagged with the source.
  4. Point a campaign at that source and calls start firing automatically.
  5. In n8n, create an incoming webhook and copy its URL.
  6. In LeadPilot: open Connectors → New connector → Webhook / API, paste the URL.
  7. Bind it to an account, a project or a single campaign — most specific wins.
  8. Hit Test — a sample call payload is delivered and logged, so you see the shape before going live.

What n8n receives on every call

{
  "agent": {
    "id": 29,
    "name": "Suraj \u2014 Banana Health"
  },
  "call_id": 43654,
  "contact": {
    "id": 8812,
    "name": "Ravi Chopra",
    "phone": "+919873002527",
    "source": "facebook_lead_ads"
  },
  "duration_seconds": 174,
  "event": "call.completed",
  "next_step": {
    "at": "2026-09-15T18:45:00Z",
    "type": "reminder_call"
  },
  "outcome": "appointment_booked",
  "project": {
    "id": 11,
    "name": "Banana Health"
  },
  "recording_url": "https://app.digitalcallers.com/api/recordings/43654",
  "score": 7,
  "started_at": "2026-09-15T18:17:02Z",
  "summary": "Registered for tonight\u0027s 7 PM masterclass; asked about doctor credentials.",
  "transcript_url": "https://app.digitalcallers.com/api/call-analysis/43654"
}

Signed with your own secret (HMAC-SHA256, X-LP-Signature), retried on failure, and dead-lettered if the endpoint keeps rejecting — so a bad hour at your end never loses a call record.

✦ Scored in~90 sec
⤷ Written back toYour CRM
app.digitalcallers.com/call-logs/43654

Call #43654 · 2m 54s · outcome: appointment booked

8 / 10
Response speed9
Conversation flow8
Booking success10
Objection handling7
Tone & personality8
Script adherence9
Intent: highTalk:listen 38:62 1 objection · answeredHinglish

Everything in that payload comes from this — the analysis DigitalCallers runs on every call.

n8n + AI calling — common questions

How long does it take to connect n8n?

Minutes, not a project. Copy one URL, paste it into n8n, send a test, and you are live. There is no onboarding fee and no professional-services engagement — if it takes longer than a coffee, something is wrong and we will get on a call.

Does connecting n8n cost extra?

No. Integrations are included in your plan — we do not charge per integration, per connection or per task. You pay for calling minutes; connecting the apps around them is part of the product.

What languages can the agent speak on these calls?

Hindi and English with natural code-switching, plus ten more Indian languages including Kannada, Tamil, Telugu, Marathi, Gujarati, Bengali, Malayalam, Punjabi and Odia. The agent follows the customer's language, which matters more than any script when the person on the other end is not comfortable in English.

Is the call recorded, and is that compliant?

Yes, recorded and transcribed, with the recording linked from the record in your own system. DigitalCallers is built for Indian regulation: DND scrubbing before dialling, calling-window enforcement, consent language in the opening, PII redaction in stored transcripts and per-client data separation.

What exactly gets written back to n8n?

Outcome, summary, intent, objections, score, duration, next step and links to the recording and transcript. The payload is documented on this page — you can see the exact JSON before you connect anything, and fire a test delivery from the dashboard to confirm the shape.

How fast is the call after a n8n record arrives?

Typically under a minute, subject to your calling window and DND rules. Speed is most of the value: answer rates fall sharply after the first few minutes, which is the whole reason to automate this rather than work a list twice a day.

Can I try this before committing?

Yes. Book a twenty-minute walkthrough and we will wire one live flow on your own account during the call, using your data — not a demo tenant with invented leads.

Also in Automation & Developer

See it running on your own n8n account

Twenty minutes, your data, no slide deck. We wire one flow live on the call.