Skip to main content

Zapier, Make and n8n apps

One app per platform on the public API and the REST-hook subscriptions (/api/v1/hooks/subscriptions, webhooks). Code and tests: integrations/zapier (Zapier Platform CLI definition, plain JavaScript, no runtime dependency), integrations/make (declarative app definition app.json plus a test runner), integrations/n8n (community-node package, TypeScript). make automation-apps-test runs the three suites (Node >= 22.18, or Docker node:lts). Tests run against a fake PBX API (test/fake-pbx.js: Bearer auth, subscriptions, click-to-call, SMS, contacts, call notes); nothing calls a real platform or PBX.

Connection​

The customer enters the PBX address and an API key (Console > Admin > API keys), sent as Authorization: Bearer <key>. Give the key integrations:write (subscriptions) plus what the triggers and actions use: the event permission of each trigger (see "Who receives what" in webhooks; a subscription for an event the key may not receive is refused with 400), self:read for click to call, SMS send and contacts. Tenant isolation is the API's: a key sees and changes only its own company.

Triggers (instant, REST hook)​

TriggerEventNotes
Call started / endedcall.started, call.ended
New voicemailvoicemail.message_left
SMS receivedsms.received
New chat messagechat.message_created
AI call summary readycall.summary_readydetail.summary holds the words (webhook-only field)
AI voicemail summary readyvoicemail.summary_ready

Turning a Zap/scenario/workflow on calls POST /api/v1/hooks/subscriptions ({target_url, event, source: "zapier"|"make"|"n8n"}); turning it off calls DELETE /api/v1/hooks/subscriptions/{id} with the id the platform kept. The answer to the subscribe carries the signing secret once. Each delivery is the event envelope {id, type, occurred_at, data}: Zapier flattens data next to id/type/occurred_at (id de-duplicates); Make exposes body.data; n8n emits the flattened object and verifies the Standard Webhooks signature (webhook-id, -timestamp, -signature, 5 minute window, rotation-safe) with the secret it stored. Zapier and Make cannot verify signatures; their target URLs are unguessable https addresses and the PBX's outbound guard applies as for every webhook.

Actions​

ActionAPIInput
Originate callPOST /api/v1/calls/click-to-calldestination, optional device id. Rings the key owner's device, then dials as that user (dial plan, permissions, toll-fraud limits apply; emergency numbers are refused).
Send SMSPOST /api/v1/sms/messagesfrom (a company SMS number), to, text. Carries an Idempotency-Key from the run, so a platform retry sends one message.
Create contactPOST /api/v1/me/contactsphone, names, company, e-mail, notes (the key owner's personal contacts).
Add call notePUT /api/v1/cdr/{call_id}/notecall id, text, private or team.

Empty optional fields are left out of the request. A PBX problem (application/problem+json) is shown with its detail and code, for example MPBX-CONTACT-NUMBER-TAKEN.

Samples (AI call summary to team call note)​

Each is the same two-step automation, and a test checks that it names real triggers, modules and fields:

  • Zapier: integrations/zapier/samples/zapier-call-summary-to-note.zap.json
  • Make: integrations/make/samples/make-call-summary-to-note.scenario.json
  • n8n: integrations/n8n/samples/n8n-call-summary-to-note.workflow.json

Review checklists (what each platform asks, where it is met)​

Publishing and review are owner work.

Zapier (public integration review). Auth with a connection test: authentication.test calls GET /me. Every trigger is a REST hook with performSubscribe, performUnsubscribe, perform and a performList sample: src/triggers.js, tested for all 7. Each action has labelled input fields and a sample: src/actions.js. Error messages are human readable: afterResponse in src/client.js. No duplicate actions on retry: Idempotency-Key on SMS. Triggers dedupe on id. At most one app per use case, no test data in the app, no hard-coded base URL (customer enters it). Still to do on Zapier's side: zapier validate, the zapier push, the review form, a public logo and a support contact.

Make (custom app / Make Apps review). Connection with a test request, one webhook per event with attach and detach, instant-trigger modules, action modules with typed parameters, human-readable error template, omitEmpty bodies: integrations/make/app.json, executed by test/runner.js. To do in Make: import the definition into the custom-app editor (components are created from the same blocks), add module descriptions and icons, and submit.

n8n (community node verification). Package keyword n8n-community-node-package, n8n block in package.json, credential with a test request, one trigger node with checkExists/create/delete webhook methods and signature verification, one action node with four operations, continueOnFail support. The node API shapes are declared locally (lib/types.ts) because n8n-workflow is not under a permitted licence for our products; the owner decides whether to build against it. Still to do: npm run build, npm publish --provenance, the verification request, an icon monopbx.svg.

Limits​

No OAuth in these apps (an API key per connection); OAuth 2.0 with the Zapier/Make/n8n consent screens is (planned). Actions act as the API key's owner. There is no polling fallback: a platform that cannot receive webhooks cannot use the triggers.