GreetKeeper reaches Zapier by webhook, so every call can go anywhere Zapier does
You catch our webhook with Webhooks by Zapier and its Catch Hook trigger. That trigger needs a paid Zapier plan, Professional or above.
Caller
“I'm calling about the quote you sent last week. Can someone ring me back today? My number is the one I'm on.”
What happened next
- Call ended, transcript and summary written to your GreetKeeper log
- Webhook posted the call.completed event to your Catch Hook address
- Your Zap created a follow-up task and pinged the owner by text
How GreetKeeper connects to Zapier
Three states, and we publish the one that is true rather than the one that reads best.
| Tool | How it connects | What that means |
|---|---|---|
| Zapier | Through Zapier |
What Zapier is, and where GreetKeeper fits
Zapier is a connector service. You build a Zap: one trigger, then one or more actions. The trigger is the thing that happened. The actions are what you want done about it.
Your GreetKeeper Zap starts with Webhooks by Zapier. Its Catch Hook trigger gives you a web address that waits for our POST.
Webhooks by Zapier needs a paid Zapier plan, Professional or above. Budget for it as its own line. Zapier's own pricing page has the current tiers.
What arrives at your Catch Hook
One signed JSON POST per event, sent to the address Zapier gave you.
GreetKeeper sends four events: call.completed, booking.created, message.taken and transfer.made. Each one carries the event type, a call id and timestamps. It carries the caller's name and number, the reason for calling, and the requested or booked time where there is one. It closes with the outcome and a link to the transcript.
From there people do the obvious things: a row in a spreadsheet, a message in a team channel, a contact in a CRM. Some send the owner a text when the reason for calling sounds like an emergency.
Your first caught test call shows you the exact field names, and a demo will too.
The call is safe whatever happens in the Zap. The transcript and the summary stay in your GreetKeeper log. We also retry the POST, with a growing gap, if the hook address doesn't answer with a 2xx.
Building your first Zap
You need a paid Zapier plan first. The rest takes about ten minutes.
Create a Zap that starts with Webhooks by Zapier
Search for Webhooks by Zapier, not for GreetKeeper, and choose the Catch Hook trigger. Zapier shows you a unique address. Copy it.
Paste that address into GreetKeeper as your webhook URL
From then on, every event is posted there. Place one test call to your GreetKeeper number, then ask Zapier to find the request. Zapier reads the field names from that sample, and every later step can reference them.
Filter on the event type, then add the action you want
A Zap that should only run on bookings needs a filter for booking.created, or it runs on every event. Then search for the app on the other side and choose its action. Give the caller's number a field to itself instead of burying it in a text blob.
Turn the Zap on, then place a second test call
Watch the run appear in your Zap history. Read what landed on the other side. A Zap that looks right in the editor and wrong in the destination is common, and this is where you catch it.
Building a Zap that holds up
Zapier runs after the call. Live answers about availability come from GreetKeeper's direct calendar connection, so pair the two for the best result.
Pick a paid Zapier plan with room for your busy weeks. Every step in a Zap counts as a task.
Our POST carries an HMAC-SHA256 signature so a receiver can prove it came from us. Treat the Catch Hook address like a password.
Keep sensitive detail out of the apps in your Zap, and map only the fields each app needs.
Questions about Zapier and GreetKeeper
How does GreetKeeper connect to Zapier?
Through our webhook, caught by Webhooks by Zapier with its Catch Hook trigger. Paste the address Zapier gives you into GreetKeeper and every call arrives there.
Do I need a paid Zapier plan?
Yes. Webhooks by Zapier needs a paid Zapier plan, Professional or above. Check Zapier's pricing page for the current tiers before you build. Some destination apps carry a plan rule of their own too.
Do I need Zapier to use GreetKeeper?
No. Calls, transcripts, summaries and calendar booking work without it. Zapier is only for pushing the finished call into another app. Make, n8n or your own server can catch the same webhook.
What happens if my Zap breaks?
The call is unaffected. It stays in your GreetKeeper log with its transcript and summary. Zapier shows the failed run in your Zap history, and you can replay it after the fix.
Can a Zap book the appointment instead of GreetKeeper?
Use GreetKeeper's calendar connection for that. It checks availability during the call, and booking is included on every GreetKeeper plan. The Zap then handles everything after.
See a real call land in a Catch Hook
Bring the app you want it in. Two minutes, no card.