Talkify / Integrations / Make
For teams who run the business on Make

Every phone call, a Make scenario.

You have automated the inbox, the forms and the invoices. The phone is the last job still run on memory and sticky notes. Talkify is the Make.com AI receptionist that answers every call in a real New Zealand voice and then posts the whole call to your scenario as tidy JSON, so Make phone call automation starts the second the caller hangs up. Scenarios you built back when Make was Integromat work just the same.

The Make logo. Talkify posts each answered call to a Make custom webhook, and Make scenarios can start calls back through the Talkify API. Make
Claim a free setup → See how it works
Connects by
Custom webhook
Sent
On hang-up
Back in
REST API

Put your name down and we will point your first call at your Make scenario and walk you through it. No setup fee, no lock-in, and your phone number stays exactly where it is.

Every call the agent answers starts a run of your Make scenario.

What Talkify hands to your scenario.

One call out as data and a way back in. Everything after that is whatever you drag onto Make's canvas.

Posts the call when it ends

Paste your Make webhook address in as a destination and every finished call is sent there as JSON, with nothing to poll and no email to parse.

Fields a module can map

Caller name, number, email and company, the summary, each captured detail as its own field, the outcome, the length and the time the phone rang.

Filters before it sends

A destination can take only one agent's calls, only calls over a set length, only after-hours calls or only certain outcomes, so your scenario runs less often.

https, headers, a signature

Posts go to https addresses only. Add your own headers if the far end wants a key, and set a secret to have each body signed with SHA-256.

Rings people from a scenario

An HTTP module calling our API starts an outgoing call with a brief and your questions, and the answers come back to Make as data.

Drops leads into Talkify

Post a lead from any app Make connects to and it lands in your Talkify leads, where your follow-up automations ring or text them.

What a missed call really costs

Your scenarios are only as good as the data that reaches them.

A missed call never becomes a bundle. The job that rang at 7:42 on a Saturday and hit voicemail does not exist anywhere Make can see. No row, no alert, no follow-up, just a caller who tried the next name on the list.

A voicemail is unstructured work. Somebody still has to listen, type it up and decide where it goes. That is the manual step your automations were meant to remove.

A call answered by Talkify arrives ready to route. Named fields, a clear outcome and a transcript behind it, posted within seconds, at any hour, however many people ring at once.

Claim a free setup → Work out your missed calls

From a ringing phone to a finished scenario run.

What happens between the tenant saying hello and the plumber being booked, with no person in the loop until one is needed.

01

The agent picks up

Your greeting, your business name, a local voice, first ring. It handles as many calls at once as come in, so a Monday morning rush is never a queue.

02

It takes down what matters

The details you asked it to collect: unit number, job type, preferred time, whatever your process needs. Each one becomes its own field, not a paragraph.

03

The call is wrapped up

A plain summary is written and the call is given an outcome, from a happy caller to one waiting on a call back. That is the field your Router branches on.

04

JSON goes to Make

Each destination whose filters match gets its own post. A slow or broken one never holds up the others, and a failed delivery shows in red on your screen.

05

Your scenario does the rest

Add a row, open a job, message the on-call manager, update a CRM. By default Make runs the scenario the moment the data arrives.

06

And can ring back

If the scenario decides someone needs a follow-up call, one HTTP request to Talkify starts it, and a second webhook brings the answers home.

What lands in your webhook

Real fields, ready to map.

This is the shape of the body your Custom webhook receives for the unit 4 call. Press Send test in Talkify and Make learns it in one go, so every module after the trigger can map the caller, the outcome and each detail the agent took down. Want us to look at your scenario with you first? We are happy to.

Talk to us → Open the payload builder
POST · Generic JSON · call.completed 
{
  "event": "call.completed",
  "agent": "Harbour Property after hours",
  "caller": {
    "name": "Aroha Ngata",
    "number": "+64 21 555 0107"
  },
  "summary": "Hot water cylinder leaking in unit 4. Switched off at the board.",
  "captured_details": { "unit": "4", "urgency": "urgent" },
  "outcome": "callback_requested",
  "duration_secs": 94,
  "called_at": "2026-09-26T07:42:08+12:00",
  "transcript_url": "https://…"
}

Who puts calls through Make.

Make turns up wherever one person has quietly become the office's integrations department. These are the businesses that ring us.

Property managers.

Maintenance calls at all hours, each one needing a job raised and the right tradie told. AI reception for real estate.

Faults · tenant calls

Trades with a back office.

Firms whose quoting and scheduling already run through scenarios, and whose phone did not. AI reception for trades.

Quotes · call-outs

Agencies and consultancies.

Teams that route every enquiry to the right person automatically and want calls routed the same way. AI reception for professional services.

Enquiries · triage

A transcript in an inbox is not automation.

Most phone answering stops at telling a person. Structured data is what lets the next step happen without one.

Branch on the outcome, not on a guess.

Because the outcome and each captured detail arrive as separate fields, a Router filter can say "outcome is callback_requested and issue contains leak" instead of text matching an email body that changes shape every time. Build the outgoing half with the payload builder.

Several routes, one scenario.

Make is at its best when a single event has to go three ways. A new enquiry, an unhappy customer and a booking change can each take their own route from one webhook, which keeps the logic in one place you can read and fix.

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 Make?
It is a phone agent that answers your business calls and then hands each finished call to Make as data. Talkify picks up in a local voice, deals with the caller, and the moment they hang up it posts who rang, what they wanted, the outcome and a link to the transcript to a Make custom webhook. Your scenario takes it from there: a row in a sheet, a job in your system, a message to the right person. Talkify is built in Christchurch for businesses in New Zealand and Australia.
How does Talkify connect to Make?
Two directions, both with no code. Out of Talkify: add a Custom webhook trigger in Make, copy the URL it gives you, and paste it into Talkify under Setup, then Call notifications, as a new destination in the Generic JSON format. Press Send test and Make sees a sample call, so it can learn the data structure before a real one arrives. Into Talkify: use Make's HTTP module with an API token from your Talkify dashboard sent as a bearer token.
What exactly does the JSON carry?
A flat, predictable body. The event name call.completed, your business and agent name, the caller's name, number, email and company where known, the summary of the call, every detail the agent captured as its own field, the outcome (for example happy, callback_requested or not_interested), the length in seconds, the time the phone rang in ISO 8601, a conversation id, and links to the transcript and recording. You decide whether the summary, the captured details and each link are included at all.
Can a Make scenario tell Talkify to ring somebody?
Yes. A POST to /api/v1/calls starts an outgoing call to one number with a topic, a brief and a short list of questions, each a yes or no, an open answer or a pick from a list, and a later question can depend on an earlier answer. Add a return_webhook pointing at a second Make webhook and the answers come back as structured data when the call ends. Our payload builder at /help/webhook-builder writes the body for you. Outgoing calls need to be switched on for your account.
Should I use Make or Zapier with Talkify?
Either works, because both give you an https webhook to post to and an HTTP step to call back. Make suits scenarios that branch: one Router can send a complaint to the manager, a new enquiry to your CRM and a booking change to the office, each route with its own filter, inside a single scenario. If you already live in Zapier, stay there. If you are building something with several paths or loops, Make is usually the tidier home for it.
Do I have to change my business phone number?
No. Your customers keep ringing the number they already know, and call forwarding sends the calls to Talkify when you want them answered: all the time, when your line is busy, when nobody picks up within a few rings, or after hours. Nothing is ported and nothing is installed, and turning it off is just as quick.
Where is my call data once it reaches Make?
The call itself is handled in New Zealand and Australian data centres and nowhere else, recordings and transcripts included. What you post to Make is a copy, held wherever your Make organisation is hosted, so choose deliberately what goes in it. Turn the summary or captured details off and they are left out at the source, and the transcript and recording links only open for someone signed in to your Talkify account.

Have a look around.

Call notifications →

The feature doing the posting: Slack, Teams, Make or your own endpoint, each with its own filters.

Prefer n8n? →

The same call data into n8n workflows, including an n8n you host yourself.

Outgoing calls →

What the agent does when a scenario asks it to ring someone: reminders, follow-ups and quick surveys.

Leads →

Where a lead posted from Make ends up, and the automations that ring or text it back.

Straight into a CRM →

On HubSpot? The direct connection files the caller and the transcript with no scenario in between.

Every integration →

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

TALKIFY FOR MAKE · NEW ZEALAND AND AUSTRALIA · 2026

The phone was the manual step.
Hand it to Make.

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.