n8n: in-call and post-call automation

n8n is the universal adapter. If your system is not in the integrations catalogue but has an API, n8n reaches it — and you build the connection by dragging boxes rather than writing code.

Two different jobs

People conflate these and then wonder why the setup does not behave. They are separate mechanisms with separate uses.

In-call: the agent triggers a workflow

Connect it

1. Build the workflow in n8n first

   Start with a Webhook node. Set the method to POST. Copy the Production URL — not the test URL, which only listens while you are watching the editor.

   Activate the workflow. An inactive workflow returns nothing and the agent is left with silence.

2. Connect n8n in Vociply

   Integrationsn8nConnect. Paste the webhook URL. If your webhook uses Header Auth, add the header name and value here too.

3. Attach it to the agent

   Select the agents that should be able to trigger it.

Building the workflow

Vociply sends two things: a one-line summary of why, and whatever data the agent gathered.

{
  "summary": "caller asked for the status of order 1042",
  "data": {
    "order_number": "1042",
    "caller_phone": "+254712345678"
  }
}

Your workflow does its work and returns JSON. Return facts, not sentences:

{
  "found": true,
  "status": "out for delivery",
  "courier": "G4S",
  "expected": "tomorrow before noon"
}

The agent turns that into speech itself — “That one’s out for delivery with G4S, should be with you before noon tomorrow.” Return a pre-written sentence and you get a stilted, obviously-scripted reply.

Telling the agent to use it

The tool is execute_n8n with action trigger_workflow. Name the trigger conditions precisely — this is one tool that can mean many things, so vagueness here produces an agent that fires it at random or never.

If the caller asks about the status of an existing order:
1. Ask for their order number.
2. Say "let me check that for you".
3. Use execute_n8n with action trigger_workflow, summary "order status
   check", and data containing the order_number.
4. Tell them what came back, in your own words.

If the workflow returns found: false, say you cannot find that order
number and offer to have someone email them. Do not guess a status.

Do not use this tool for anything other than order status questions.

Post-call: reacting to lead events

The second job, and the one most people get more value from. As a lead moves through Lead Callback, Vociply emits events and delivers them to your connected workflow destinations.

{
  "event": "lead.qualified",
  "lead": {
    "name": "Amina Otieno",
    "phone": "+254712345678",
    "email": "amina@example.com"
  },
  "qualification": {
    "owns_property": true,
    "monthly_bill": 4800
  }
}

Build one workflow with a Switch node on event and a branch each. Deliveries are queued and retried rather than sent inline, so a slow or briefly unavailable endpoint never delays a dial — and each delivery is recorded, so “did my workflow get told?” is answerable without reading logs.

Locking it down

A webhook URL is a credential. Anyone who learns it can run your workflow, and if that workflow writes to your systems, that matters.

• Use Header Auth on the n8n webhook node and set the matching header name and value in the Vociply connection. This is the single most important step.
• Validate the input. Do not pass data straight into a database query or a shell command.
• Prefer read-only workflows for in-call use. Lookups are safe to get wrong; writes triggered by a mis-heard sentence are not.
• Use HTTPS and a properly reachable host. Local and internal addresses are refused when you connect, deliberately.
• Log what ran. When something odd happens on a call, the n8n execution history is where you find out what was actually asked for.

Recipes worth stealing

Questions