Call Event Webhooks — Real-Time Phone System Notifications

Your phone system, talking to the rest of your business.

Every time a call comes in, every time one is answered, every time one ends — Nehos can fire a real-time notification to your CRM, your ERP, your call tracking platform, or any system you build. No polling, no overnight syncs, no manual data entry.

If your software can listen for HTTPS, our phone system can talk to it.

What you can do with it

A few things our customers are already using it for, or asking about:

• Screen pop on incoming calls — your reception sees who’s calling before they pick up, with the matching record open in your CRM.
• Automatic call logging — every call ends up as an activity in your CRM with the right contact, duration, and disposition. No one types it in.
• Missed call follow-up — when a call goes unanswered, your sales platform automatically queues a callback task.
• Lead source attribution — your marketing dashboard knows which advertised number generated which call, and what it turned into.
• Bespoke business logic — fire workflows in n8n, Zapier, Make, or any custom script when a specific number rings, when a VIP customer calls, when a call lasts more than five minutes — whatever you want.
• AI on top of voice — feed call events into a model that summarises the day, flags trends, or routes hot calls in real time.

If it’s a system you talk to with a webhook, we can wire it into your phone system.

What gets sent

When a call hits your account, we send a small JSON message to the URL you give us. Here’s what your endpoint receives when an incoming call starts ringing:

{
  "event": "event_call_started",
  "event_time_info": {"date": "2026-05-20", "time": "15:49:15", "timestamp": 1779256155},
  "payload": {
    "number": "0491570156",
    "did": "0731071900",
    "linked_id": "1779256155.36574",
    "call_started_datetime": "2026-05-20 15:49:15",
    "state": "RingOut",
    "is_pbx_inbound_call": true
  }
}

You can subscribe to whichever events you actually need:

The same number that called, the same Nehos number it hit, a unique call ID, timestamps, duration, answered status, and the trunk info — it’s all in there.

Authentication — your endpoint, your rules

We support every common webhook auth pattern, so we plug into whatever your platform expects:

• Static API key in a custom header (X-Your-App-Key, X-Webhook-Token, anything)
• HTTP Basic (username + password)
• Bearer token
• OAuth 2.0 Client Credentials (standard server-to-server flow)
• No auth (rare, but available if your endpoint is internal-only)

Tell us what your developer needs and we configure it on our side.

Source IP / firewall pinning

All webhooks come from a static IP on our Brisbane infrastructure. If you want to lock your endpoint down so only Nehos can talk to it, we’ll give you the IP to allowlist.

Getting set up

It’s a same-day job once we have the details. The conversation usually goes like this:

1. Tell us what you want to do. A sentence or two is enough — “log every inbound call into HubSpot”, “fire a Slack message when a VIP rings”, “feed call data into our reporting warehouse”.
2. We ask your developer four things: the URL(s) you want us to send events to (must be HTTPS); which events you care about (most customers want started + finished); how your endpoint authenticates (header, bearer, OAuth, basic, none); any extra fields you want — we can include custom headers on every request.
3. We configure it on your phone account and run a test call to your number to confirm the data lands correctly in your system.
4. You go live the same day if you’re ready.

If you don’t have a developer, we’ll work with whoever supports your existing CRM or business software — Nehos staff can talk to them directly and handle the integration on both sides.

What if my CRM expects a different payload shape?

• Your developer adapts the receiver to read what we send (cleanest, no middle layer, faster). The field names are listed above — most platforms can map them in minutes.
• We translate on our side to whatever shape your platform expects. Slightly more setup, but useful when you’re integrating with an off-the-shelf product whose webhook receiver you can’t change.

Either is part of the service.

What it’s not

Honest about scope:

• It’s not a polling API. You don’t query us for call data; we push to you in real time. If you also want to pull historical data, ask — we have a separate call-records API for that.
• It’s not a fully managed integration to specific named platforms. It’s a webhook stream — your developer (or ours, if you don’t have one) wires the last mile.
• It’s not retroactive. Once it’s configured, events flow for new calls. Historical calls aren’t replayed.

Pricing

Pricing is matched to your setup. Most existing Nehos phone accounts get this included — it depends on your plan and event volume. Send us your account code and what you’re planning to do with it and we’ll come back with a number.

How to get it

If you’re an existing Nehos customer: reply to your account email or open a ticket at support@nehos.net with a one-line description of what you want to build.

If you’re new to Nehos: have a chat with us first about your phone system — this works best as part of a properly designed setup, not bolted onto something we didn’t build.

📞 1300 726 889 | ✉️ sales@nehos.net