Zapier integration
Last updated: 2026-06-15
The Drömlik–Zapier integration lets you turn any phone-system event into an automated workflow. Drömlik pushes events to a Zap via a webhook trigger, Zapier does the rest — log a call in your CRM, post a missed-call alert to Slack, create a Trello card from a voicemail, the list goes on.
How it works
Each Zap starts with a Zapier Webhooks by Zapier trigger (Catch Hook). Zapier gives you a unique URL, you paste that URL into Drömlik's webhook settings, and Drömlik posts the event payload to Zapier whenever the event fires. From there, any of Zapier's 6,000+ apps can act on it.
Connect Drömlik to Zapier
- 1
Create a Zap with a Catch Hook trigger
In Zapier, create a new Zap. Choose Webhooks by Zapier as the trigger app and Catch Hook as the trigger event. Zapier displays a unique webhook URL — copy it.
- 2
Add the webhook to Drömlik
In the Drömlik admin console, go to Integrations → Webhook. Click Add, paste the Zapier URL, set the request method to POST, and enable the events you want to forward (see the table below).
- 3
Send a test event
Click Test in Drömlik. Then in Zapier click Test trigger — the event payload should appear so you can map fields downstream.
- 4
Add actions in Zapier
Add any Zapier action — Slack message, Google Sheets row, HubSpot contact update, etc. Map fields from the Drömlik payload (caller number, extension, call duration, recording URL, …) into the action.
- 5
Turn the Zap on
Save and publish the Zap. From now on, every matching Drömlik event will trigger your workflow.
Available triggers (events)
Drömlik can push any of the events below into Zapier. Pick only the ones a given Zap actually needs — high-volume events like Call state changed (30011) and Extension call state changed (30008) can burn through Zapier tasks fast.
| Code | Trigger | What it fires on |
|---|---|---|
30005 | Organization status switch state changed | The organization feature status changed. |
30006 | Organization structure changed | Departments, job titles or assignments changed. |
30007 | Extension registration status changed | An extension registered or unregistered on a SIP endpoint or the Drömlik App. |
30008 | Extension call state changed | The call state of an extension changed (idle, ringing, talking, …). |
30009 | Extension presence state changed | An extension's presence (Available, Away, DND, …) changed. |
30010 | Trunk registration state changed | A SIP trunk registered or lost registration. |
30011 | Call state changed | Real-time status update for any active call. |
30012 | Call end details (new CDR) | A call ended and a CDR is now available. |
30013 | Call transferred | An active call was transferred. |
30014 | Call forwarded | An inbound call was forwarded because of an extension rule. |
30015 | Call failure | A call could not be initiated. |
30016 | Incoming call request | An inbound call arrived on a monitored trunk. |
30017 | DTMF digit pressed | A caller pressed a key during a call. |
30018 | Prompt playback completed | A custom audio prompt finished playing. |
30019 | Satisfaction survey feedback | A caller submitted a post-call survey response. |
30020 | uaCSTA call report | Call status change for an extension controlled via uaCSTA. |
30022 | Extension information updated | An extension was created, edited, or deleted. |
30023 | Trunk information updated | A trunk was created, edited, or deleted. |
30024 | No host in audio conference | The host left an audio conference. |
30025 | Agent automatic pause | A queue agent was auto-paused after too many missed calls. |
30026 | Agent ringing timeout | A queue agent missed a call due to ring timeout. |
30027 | Call report download ready | An asynchronously generated call report is ready to download. |
30028 | Call note status updated | A call note became editable or read-only during a call. |
30029 | Agent status changed | A queue agent's status changed (logged in/out, paused, …). |
30030 | Bulk message sending failed | Some messages in a message campaign failed to send. |
30031 | New message notification | An inbound message arrived on a connected message channel. |
30032 | Message sending result | Delivery status changed for a message sent through the API. |
30033 | Recording download completed | An asynchronously requested recording file is downloaded. |
30034 | System event (information) | An information-level system event occurred. |
30035 | System event (warning) | A warning-level system event occurred. |
30036 | System event (alert) | An alert-level system event occurred. |
Popular Zap recipes
- New CDR → Google Sheets row. Trigger:
30012. Use it to build a lightweight call log. - Missed call → Slack DM. Trigger:
30015(Call failure) filtered to no-answer hangups. - New voicemail → email + Trello card. Trigger:
30012filtered to calls that ended in voicemail. - Extension presence → Microsoft Teams status. Trigger:
30009. - Trunk down → PagerDuty incident. Trigger:
30010when status is unregistered. - Inbound SMS → HubSpot note. Trigger:
30031.
Payload format
Every event is delivered as a JSON POST body. Drömlik includes the event code, a timestamp, and an event-specific payload. Use Zapier's "Catch Raw Hook" if you need the full body, or "Catch Hook" if you'd like Zapier to parse top-level fields automatically. See Webhooks overview for the canonical schema.
Security
Drömlik signs each webhook request with the shared secret you configure. In Zapier you can add a Filter by Zapier step that validates the signature before the rest of the Zap runs — or use a Code by Zapier step for HMAC verification. Treat the Zapier hook URL itself as a secret and rotate it if it leaks.
Limits to keep in mind
- Each Zap run consumes one Zapier task. Plan accordingly for high-volume events.
- Zapier's free plan polls/runs at most every 15 minutes for some triggers; the webhook trigger fires in near real-time.
- Drömlik retries failed deliveries a few times before dropping the event — don't rely on Zapier as the sole record of truth for critical data.