Talkify / Integrations / n8n
For n8n, in the cloud or on your own box

Your phone line, wired into n8n.

You chose n8n because you like owning the plumbing. Talkify is the n8n AI receptionist that fits that thinking: it answers every call in a real New Zealand voice, then hands the finished call to your Webhook node, signed if you want it to be, so an n8n phone call workflow runs on a self-hosted instance as happily as on n8n Cloud.

The n8n logo. Talkify posts every answered call to an n8n Webhook node, and n8n workflows can start calls through the Talkify API. n8n
Claim a free setup → See how it works
Trigger
Webhook node
Signed
HMAC SHA-256
Runs on
Cloud or your box

Put your name down and we will get calls flowing into your n8n workflow and walk you through it. No setup fee, no lock-in, and your phone number stays exactly where it is.

Every answered call runs your n8n workflow, on your own server if you like.

Built for people who read the payload.

Nothing clever and nothing hidden: a documented body, a signature you can check, and an API to answer back with.

Feeds a Webhook node

Every finished call is a POST to the production URL of your Webhook node. One destination per workflow, or several, each with its own filters.

Signed with your secret

Set a secret and each post carries a hex SHA-256 HMAC of the raw body in X-Talkify-Signature, ready for the Crypto node to check.

Header Auth friendly

Add any header name and value to the destination to match the credential on your Webhook node. Headers are stored encrypted on our side.

Cloud or self-hosted

Any public https address works, so an n8n running in Docker in an Auckland or Sydney data centre gets the same data as n8n Cloud.

Predictable JSON

Caller, summary, each captured detail as its own key, outcome, length in seconds, ISO 8601 start time, conversation id and transcript link.

An API to reply with

An HTTP Request node can start one call or a batch, with questions, and have the answers posted back to another Webhook node.

The price of the unanswered line

A workflow cannot fix a call nobody took.

For a support desk, the phone is the escalation channel. People ring when email has already failed them. If that call rolls to voicemail at eight in the morning, the first thing your client learns is that you were not there.

A voicemail has no fields. No company, no urgency, no outcome to branch on, so it sits outside every workflow you have built until a person clears it.

Talkify answers every call, all at once, at any hour, and turns each one into a request your If node can route in milliseconds. The engineer gets a ticket with the facts, not a garbled message to decode.

Claim a free setup → Count what you are missing

From the first ring to a green execution.

One call, followed all the way into your Executions list.

01

Answered on the first ring

Your business name and greeting in a local voice, whatever the hour. Ten people ringing at once are ten conversations, not a hold queue.

02

The facts, collected

The agent asks what you told it to: the client, what is affected, how urgent it is. Each answer is kept as a named detail rather than buried in prose.

03

Summarised and scored

When the caller hangs up the call gets a short summary and an outcome, such as callback_requested, happy or unhappy, the value your workflow switches on.

04

Posted and signed

The JSON goes to your Webhook node over https with your headers and, if you set a secret, a signature over the exact bytes sent.

05

Your nodes take over

Verify, branch, write to Postgres, open the ticket, post to the team channel. It all happens on infrastructure you chose.

06

The loop closes

If the workflow wants a follow-up call, an HTTP Request node asks Talkify to make it, and the answers land back in n8n as their own execution.

What your Webhook node receives

A request you can read and verify.

This is the request behind the Kōwhai Accounting call. The body is plain JSON with the same keys every time, and the signature header is the hex SHA-256 HMAC of those exact bytes under your secret, so a Crypto node can prove it came from Talkify before any other node runs. Want a second pair of eyes on your workflow? Talk to us.

Talk to us → Open the payload builder
Request · call.completed 
POST /webhook/talkify-calls
Content-Type: application/json
X-Talkify-Signature: 9f2c41…d07e41a

{
  "event": "call.completed",
  "caller": {
    "name": "Sam Rewi",
    "number": "+64 3 555 0164",
    "company": "Kōwhai Accounting"
  },
  "summary": "Whole office without email since 7.45am.",
  "captured_details": { "affected": "whole office" },
  "outcome": "callback_requested",
  "duration_secs": 71,
  "conversation_id": "conv_…"
}

Who runs Talkify through n8n.

The businesses that pick n8n tend to care where data lives and like to see exactly how things work. So do we.

IT and managed service providers.

Support lines that must be answered at eight in the morning and turned into tickets without retyping. AI reception for professional services.

Outages · tickets

Accountants and bookkeepers.

Firms holding client financial data who would rather run their automation on a server they control. AI reception for accountants.

Client calls · deadlines

Clinics that guard their data.

Practices that want patient calls answered and logged, with every copy of the details kept close to home. AI reception for clinics.

Bookings · messages

Keep the data where you put it.

Self-hosting n8n is a decision about control. The phone side deserves the same care.

Local calls, local handling.

Talkify handles every call in New Zealand and Australian data centres, recordings and transcripts included. Pair that with an n8n you host in the same region and the whole path, from the caller's voice to your ticket, stays in places you can name to a client or an auditor.

Send only what the workflow needs.

Switch the summary, the captured details or either link off and they are removed before anything leaves Talkify, not merely hidden. Draft the outgoing call body for your HTTP Request node with the payload builder, which runs entirely in your browser.

The Talkify difference

Built here.
Not badged here.

Most AI answering services sold in New Zealand are overseas platforms with a local logo. Talkify runs on our own local SIP network, keeps data in New Zealand and Australian data centres, and answers in voices your callers actually recognise. That changes how every call sounds, and where every recording lives.

Ask a person Talk to us

Tell us which system you run and how your calls come in. A real person at Talkify replies, and we set the connection up with you.

Talk to us →

Flat NZD pricing, published on the site. No setup fee. No lock-in. Built in Ōtautahi Christchurch and operated by Talkify Limited.

  1. 01

    Calls never leave the neighbourhood.

    We run our own local SIP carrier network, so your calls connect close to home. Less lag, no talking over each other, and the clear, close sound of a local call.

    Local SIP · pickup from 0.4s
  2. 02

    Voices from here, for callers from here.

    A full range of Kiwi and Aussie voices, not an American accent doing its best. Callers relax when the voice sounds like them, and relaxed callers book.

    EN-NZ · EN-AU · 32 voices
  3. 03

    A local number in every region.

    Regional phone numbers across New Zealand and Australia, so a Christchurch caller rings 03 and an Auckland caller rings 09. Local numbers get answered; unknown ones get screened.

    NZ & AU regional DDIs
  4. 04

    Your data stays on this side of the world.

    For data sovereignty, everything is stored in New Zealand and Australian data centres: recordings, transcripts and customer details held close to home under local privacy law.

    NZ + AU data centres · AES-256
  5. 05

    Agents that make the call, too.

    Full outbound service, not just answering. Your agents confirm bookings, chase missing details and run marketing call campaigns, with every conversation transcribed.

    Confirmations · Campaigns
  6. 06

    Campaigns that actually get answered.

    Load a contact list and the agent rings through it, asks your questions, and hands back transcripts with the answers extracted and analysed. Offers, follow-ups or a straight survey, at a scale no clipboard reaches.

    AI phone campaigns
  7. 07

    Call centre scale without the call centre.

    One agent or a whole fleet answering unlimited simultaneous calls. Overflow, after-hours or the entire front line, with warm transfer to a human whenever it matters.

    ∞ concurrent lines
  8. 08

    Plugged into the tools you already run.

    Calendars, CRMs like HubSpot and GoHighLevel, gym platforms, WhatsApp and SMS, plus Zapier and a full REST API when you want to wire up something custom.

    CRM · Calendar · Zapier · API
  9. 09

    We set it up. Personally.

    No DIY prompt wrangling. We build your agent around your business, brief it on your services and pricing, tune it with you, and keep tuning after you're live.

    Done-for-you setup
  10. 10

    Every call in your pocket.

    Native apps for iPhone and Android push you each call summary the moment it ends: who rang, what they wanted, what the agent did about it.

    iOS · Android
  11. 11

    Reporting that reads the room.

    Full transcripts, sentiment, outcomes and intent on every call, rolled into dashboards that show what your callers actually want, not just how many rang.

    Transcripts · Sentiment · Intent

Frequently asked.

The questions we hear most. If yours isn't here, talk to us and a person will answer it.

What is an AI receptionist for n8n?
A phone agent whose output is an n8n trigger. Talkify answers your business line in a natural New Zealand or Australian voice, handles the caller, and when the call ends it sends the caller's details, the summary, what the agent captured, the outcome and a transcript link to the Webhook node at the start of your workflow. From there your workflow owns it: open a ticket, write to your database, page the person on call.
How do I connect Talkify to n8n?
Add a Webhook node set to POST and copy its production URL, not the test one: the test URL only listens while you are watching the editor, which is the most common reason a first real call seems to vanish. In Talkify, go to Setup, then Call notifications, add a destination in the Generic JSON format and paste the URL in. If your Webhook node uses Header Auth, add the same header name and value to the destination. Press Send test to see a sample call arrive.
Does it work with a self-hosted n8n?
Yes. Talkify posts to any https address it can reach over the internet, so an n8n on your own server, a VPS or a container behind a reverse proxy works exactly like n8n Cloud. It needs a public https address with a valid certificate, because we never send caller details over plain http. An instance that only exists on your office network needs a tunnel or a proxy in front of it.
How can my workflow check a request really came from Talkify?
Set a signing secret on the destination. Every post then carries an X-Talkify-Signature header: the hex SHA-256 HMAC of the exact body, keyed by your secret. In n8n, turn on the Webhook node's Raw Body option, compute the HMAC of that body with the Crypto node or a Code node, and compare it with the header before anything else runs. You can use Header Auth on the Webhook node as well, or instead.
Can an n8n workflow make Talkify ring or text people?
It can start calls. An HTTP Request node posting to /api/v1/calls, with your Talkify API token as a bearer token, rings one number with a topic, a brief and your questions, and /api/v1/calls/batch takes a list. Give it a return_webhook that points at a second Webhook node and the answers arrive back in n8n when the call finishes. A POST to /api/v1/leads creates a lead instead, and your lead automations decide whether to ring or text them.
Do I need a new phone number?
No. Keep the number on your website, your van and your invoices. You forward calls to Talkify from your current provider, whenever suits: every call, only when the line is engaged, only when nobody answers, or only out of hours. Nothing is ported, and undoing it takes a minute.
Does sending calls to n8n keep the data in New Zealand or Australia?
The call is handled in New Zealand and Australian data centres and nowhere else, recordings and transcripts included. The copy you send to n8n goes wherever that n8n runs. Host it yourself in a New Zealand or Australian data centre and the copy stays in a place you choose and control; use n8n Cloud and it is held where n8n hosts it. Either way you can leave the summary and captured details out, and the transcript link only opens for someone signed in to your Talkify account.

Have a look around.

Call notifications →

Where you add the n8n destination, alongside Slack and Teams, with filters and plain English routing.

Using Make instead? →

The same call data into Make scenarios, for teams who prefer a hosted canvas.

Outgoing calls →

Reminders, follow-ups and short surveys, started from your workflow with one request.

Leads →

Post a lead from n8n and let Talkify ring or text it back within about a minute.

A CRM without the workflow →

On Pipedrive? The direct connection greets callers by name and files the call for you.

Every integration →

Everything Talkify connects to, and what your agent can do once it is connected.

TALKIFY FOR N8N · NEW ZEALAND AND AUSTRALIA · 2026

Your workflows are ready.
Now answer the phone.

We connect it to your system with you Talk to us Sign up, sales & support · we'll set you up 0800 002 967
● No card● No lock-in● Free to call● Set up alongside you

Or run it from your pocket

Download Talkify Mobile on the App Store Get Talkify Mobile on Google Play
Get your first agent · No card needed

Talkify is currently available to businesses in New Zealand & Australia only.

Personal Assistant
Single mobile or landline. Built for one person, not a business.
$89/mo
Shortwave plan

Founding rate On a monthly plan your price is locked in at the founding rate for your first 3 months, then the standard rate applies. Pay as you go has no founding step: the rate is just the rate. Plans include 50 to 200 minutes a month, then 10c a minute. The first 20 texts each month are free, then 9c each.

● Your data stays in NZ.