Overdue Invoice Payment Reminder Call

When an Edesy Invoice invoice goes overdue, an AI voice agent calls the customer, reminds them of the amount, shares the payment link and records a promise-to-pay date. Setup with the invoice.overdue webhook, n8n or Make and the Calls API, plus the Edesy Collect alternative.

6 min readUpdated

When an Edesy Invoice invoice turns overdue, an AI voice agent calls the customer within minutes, states the invoice number and balance, points to the payment link and asks for a payment date. A 2-minute call costs about ₹12 at ₹6 a minute, plus telephony. The overdue event has no phone, so the flow looks it up.

Works with: Edesy Invoice via webhooks in n8n or Make (or your server, via API) · fixed-message reminders at scale Native in Edesy Collect (load debtors by API or paste) · Native Invoice to Voice or Invoice to Collect: planned

Note A native "call overdue customers" switch in Edesy Invoice is planned. Request early access.

How it works#

invoice.overdue webhook ──> n8n / Make
 (number, customerId,         │ 1. verify X-Edesy-Signature
  balance, dueDate,           │ 2. GET /api/v1/customers/:id  -> phone, name
  publicToken)                │ 3. pay link = https://invoice.edesy.in/p/<publicToken>
                              ▼
                    POST /api/v1/calls ──> AI reminder call ──> call.analyzed
                                                                  │ promise_date?
                                                                  ▼
                                  record promise on the invoice, or schedule a follow-up

Before you start#

  • An Edesy Invoice organisation at invoice.edesy.in where customers have a phone number (on the customer, or on a contact person).
  • An Invoice API key: Settings → Data & developers → API keys → New key (admin only; starts with inv_).
  • A voice agent, its ID, and a voice agent API key (vp_live_...).
  • An n8n or Make account, or a server endpoint.
  • Optional: a WhatsApp Business account in n8n or Make to send the payment link in writing.

Set it up (n8n)#

  1. In n8n, add a Webhook node, method POST, Respond: Immediately. Copy the Production URL.
  2. In Edesy Invoice, open Settings → Data & developers → Webhooks, click New webhook, paste the URL as the Endpoint URL, tick invoice.overdue under Events (and invoice.paid if you want to stop follow-ups), and click Create webhook. Copy the Signing secret shown once. The Free plan allows 1 webhook.
  3. Verify each delivery in a Code node: X-Edesy-Signature is sha256= plus the hex HMAC-SHA256 of the raw body with your signing secret. The event name is also in X-Edesy-Event.
  4. Add an HTTP Request node to fetch the customer:
GET https://invoice.edesy.in/api/v1/customers/{{ $json.body.data.customerId }}
Authorization: Bearer inv_xxxxxxxx

Use phone; if it is empty, use the phone of the contact person with isPrimary: true. Stop if there is no number. 5. Optional: send the payment link by WhatsApp first. The link is https://invoice.edesy.in/p/{{ publicToken }}, the invoice's public page with the pay button. 6. Add an HTTP Request node to place the call:

POST https://voice-agent.edesy.in/api/v1/calls
Authorization: Bearer vp_live_xxxxxxxx
Idempotency-Key: overdue-{{ $('Webhook').item.json.body.data.number }}
Content-Type: application/json

{
  "agentId": 1042,
  "phoneNumber": "{{ $json.phone }}",
  "variables": {
    "customer_name": "{{ $json.displayName }}",
    "invoice_number": "{{ $('Webhook').item.json.body.data.number }}",
    "balance": "{{ $('Webhook').item.json.body.data.balance }}",
    "due_date": "{{ $('Webhook').item.json.body.data.dueDate }}",
    "pay_link_sent": "yes",
    "public_token": "{{ $('Webhook').item.json.body.data.publicToken }}"
  },
  "retry": { "enabled": true, "maxAttempts": 2, "delayMinutes": 120, "dispositions": ["NO_ANSWER", "BUSY"] }
}
  1. Activate the workflow.

Record the promise-to-pay date#

  1. In the agent's Behavior tab, open Post-Call Extraction, click New Template and add a field with Field Key promise_date, Data Type Text, and AI Description "Date the customer promised to pay, as YYYY-MM-DD, empty if none".
  2. Subscribe a second n8n workflow to call.analyzed (Settings → Webhooks → Add Webhook).
  3. When extracted_data.promise_date is set, record it on the invoice with the same endpoint the customer's own "I'll pay on" button uses:
POST https://invoice.edesy.in/api/public/documents/<publicToken>/promise
Content-Type: application/json

{ "date": "2026-11-28", "note": "Promised on AI reminder call" }

This pauses Invoice's own reminders until that date and emits invoice.promise_to_pay. The public_token you passed as a variable comes back in call.analyzed under variables.

Alternative: Edesy Collect#

Edesy Collect is built for volume: one recorded-style reminder per campaign, caller-ID rotation, attempt caps and calling hours enforced on the server. From the same n8n flow, add the customer to a running reminder campaign:

POST https://voice-api.edesy.in/v1/collect/campaigns/CAMPAIGN_ID/contacts
Authorization: Bearer sk_your_api_key

{ "contacts": [{ "phone_number": "+919800000000", "name": "Ravi Traders", "due_date": "2026-11-15", "amount_due": 18500 }] }

Collect speaks the same message to every debtor (it does not read each amount aloud yet), does not take a promise on the call, and has no payment link. Mark debtors paid with POST/v1/collect/contacts/:id/paid when invoice.paid arrives. Plans: ₹1,499, ₹3,499 or ₹10,499 a month.

Data map#

Direction Field Meaning
From Invoice data.number, data.balance, data.total, data.currency, data.dueDate Invoice number, amount still due, due date
From Invoice data.customerId Used to fetch phone and displayName
From Invoice data.publicToken Builds the pay link /p/<publicToken> and the promise endpoint
Into the call variables.customer_name, invoice_number, balance, due_date Used in the prompt
Back in call.analyzed disposition For example SUCCESS (agreed to pay), CALLBACK_REQUESTED, NOT_INTERESTED (dispute), WRONG_NUMBER, DO_NOT_CALL
Back extracted_data.promise_date, extracted_data.dispute_reason From your extraction template
Back call_summary, variables.public_token Notes for your accounts team; key to write back

Sample agent prompt#

You are Meera from the accounts team of Sai Packaging, Bhiwandi. You are calling
{{customer_name}} about invoice {{invoice_number}} for ₹{{balance}}, which was due on
{{due_date}}.

Start in Hindi ("Namaste, main Sai Packaging ke accounts se Meera bol rahi hoon"), and
switch to English or Marathi-accented Hindi if they prefer. Be polite and brief.
1. Confirm you are speaking to the right person or the accounts contact.
2. Say the invoice number, the amount and that it is overdue.
3. Tell them the payment link has been sent on WhatsApp and works with UPI, cards and
   net banking.
4. Ask when they will pay and repeat the date back.
5. If they dispute the invoice, note the reason and say the team will call back.
Never threaten, never mention legal action, never ask for card or OTP details.
Set SUCCESS when they give a payment date, CALLBACK_REQUESTED if the right person is not
available, NOT_INTERESTED for a dispute, WRONG_NUMBER, or DO_NOT_CALL if asked.

Test it#

  1. Create a test customer with your own phone number and a test invoice with a due date in the past.
  2. Wait for Invoice's daily overdue check, or send the webhook to n8n yourself with a sample body from the delivery log.
  3. Answer, promise a date, hang up. Check that the invoice now shows the promised date and that the invoice.promise_to_pay webhook fired.
  • You are calling an existing customer about their own invoice, a transactional call. Keep it to the debt and the payment.
  • Edesy does not scrub numbers against the NCPR (DND) registry.
  • Follow RBI's fair practices if you are a lender or NBFC: call between 8 am and 7 pm, no harassment, no third-party disclosure. Otherwise, use a 9 am to 9 pm window under Settings → Call Settings → Calling Window.
  • Add customers who ask not to be called to Settings → Blocked Numbers and switch them to written reminders.

What it can't do yet#

  • The invoice.overdue event has no phone or customer name; you need the customer lookup step.
  • Invoice has no built-in connection to the voice agent or to Collect.
  • The agent can't take a payment on the call; it points to the link.
  • The promise is recorded through the public portal endpoint, so it appears as if the customer set it.

FAQ#

When does the call happen? As soon as Invoice sends invoice.overdue (when its overdue check marks the invoice) and your workflow runs, inside your calling window.

What does a reminder cost? About ₹6 to ₹12 for a 1–2 minute AI call plus telephony. With Collect, a connected call is ₹0.90 or less depending on plan, and unanswered calls are free.

AI agent or Collect: which should I use? Use the AI agent when the conversation matters: B2B customers, disputes, promise dates. Use Collect for large lists where one standard reminder is enough.

Can it call before the due date? Not from this event: invoice.overdue fires after the due date. To remind earlier, start the call from your own schedule (for example a daily n8n run over a sheet of upcoming dues) with the same Calls API request.

Does it stop once the customer pays? Subscribe to invoice.paid and skip or cancel follow-up calls for that invoice. A call already in progress is not stopped.

Start free · Book a demo · Don't see your app? Request it

Was this page helpful?