Documentation

1) App registration

1. Azure portal → Microsoft Entra ID → App registrations → New registration.
2. Name: MeetFlow.
3. Supported account types: «Accounts in this organizational directory only» (single-tenant) or «Accounts in any organizational directory» (multi-tenant).
4. Redirect URI (Web): copy from MeetFlow, e.g.
   https://dev.lireno.ch/wp-admin/admin.php?page=meetflow-settings&auth=microsoft

2) IDs and client secret

3) API permissions

1. API permissions → Add a permission → Microsoft Graph → Delegated permissions.
2. Enable: Calendars.ReadWrite, OnlineMeetings.ReadWrite, User.Read.
3. Grant admin consent.

4) Connect in MeetFlow

1. Paste values → Save Settings → Connect with Microsoft.
2. Select Microsoft Teams → Test connection.

Error AADSTS50194: Use your Directory (tenant) ID, not common, for single-tenant apps.

1) Create OAuth app

1. Zoom Marketplace → Develop → Build App → OAuth → User-managed app.
2. App name: MeetFlow.

2) Redirect URL and scopes

3) Copy credentials

Activate the app in Marketplace (not draft only).

4) Connect in MeetFlow

1. Save Settings → Connect with Zoom → test booking.

Zoom Pro account or higher recommended.

1) Project & API

1. Select or create your Google Cloud project.
2. Enable Google Calendar API (APIs & Services → Library).
3. OAuth branding is configured on the consent screen (step 2).

2) OAuth consent screen

APIs & Services → OAuth consent screen

3) OAuth client

Credentials → Create credentials → OAuth client ID

4) Enter in MeetFlow

1. Save settings → Connect with Google → select «Google Meet» provider.

1) Create integration

1. developer.webex.com → My Webex Apps → Create a new app → Integration.
2. Redirect URI(s): https://dev.lireno.ch/wp-admin/admin.php?page=meetflow-settings&auth=webex

2) Scopes

Enable: meeting:schedules_read, meeting:schedules_write.

3) OAuth credentials

4) Connect in MeetFlow

1. Save Settings → Connect with Webex → Test connection.

Option A — Meta Cloud API

Option B — Twilio WhatsApp Sandbox

Select provider Twilio in MeetFlow (not Meta).

1) Create bot

2) Get chat ID

1. Message your bot, open https://api.telegram.org/bot<TOKEN>/getUpdates.
2. Copy chat.id from JSON.

1) Account Info

2) Phone number

3) Configure SMS Reminder

1. Enable Send SMS reminders before meetings.
2. Placeholders: {name}, {date}, {time}, {meeting_link}, {hours}.
3. Save Settings.

4) Test

1. Test booking with mobile number → check SMS / Twilio Messaging logs.

1) Set up a webhook

1. Webhook URLs: one URL per line — examples:
   • Zapier Catch Hook: https://hooks.zapier.com/hooks/catch/…/…/
   • n8n Webhook node: https://your-n8n.example.com/webhook/meetflow-booking
   • Make Custom webhook: https://hook.eu1.make.com/…
   • Testing: webhook.site
2. Events: enable «Booking created» and/or «Booking cancelled».
3. Optional signing secret: MeetFlow signs requests with the X-MeetFlow-Signature header (HMAC SHA-256 over the body, format sha256=…).
4. Save settings — the test button only reads saved URLs.
5. Click «Send test webhook» → success message «Test webhook sent successfully».

2) Payload

Test event: webhook.test. Real events: booking.created / booking.cancelled with full booking data:

{
  "event": "booking.created",
  "timestamp": "2026-07-08T12:00:00+00:00",
  "site_url": "https://your-site.com",
  "booking": {
    "id": 42,
    "booking_id": "MF-20260708-ABC",
    "status": "confirmed",
    "customer_name": "Jane Doe",
    "customer_email": "jane@example.com",
    "customer_phone": "+41791234567",
    "booking_date": "2026-07-15",
    "booking_time": "10:00",
    "duration": 30,
    "timezone": "Europe/Zurich",
    "provider": "teams",
    "meeting_url": "https://teams.microsoft.com/…"
  }
}

Headers: Content-Type: application/json, X-MeetFlow-Event, optional X-MeetFlow-Signature.

Webhooks are tool-agnostic — the same URL works with Zapier, n8n, Make and custom apps. Detailed guides: Zapier · n8n · Make.

Option A — Instant trigger (Catch Hook)

1. In Zapier: Create Zap → trigger «Webhooks by Zapier» → «Catch Hook».
2. Copy the hook URL shown (format https://hooks.zapier.com/hooks/catch/…/…/).
3. In MeetFlow: paste it into Settings → Integrations → Webhook URLs → enable «Booking created» → save.
4. Click «Send test webhook» → in Zapier click Test trigger → sample data appears.
5. Add an action in Zapier (e.g. Gmail, Slack, Google Sheets, WaNotifier) and map fields from booking.
6. Publish the Zap → make a real test booking.

Option B — Polling (REST API with API key)

Endpoint and API key details: Automation API (Scale). In Zapier: trigger «Webhooks by Zapier → GET» with the bookings endpoint and header X-MeetFlow-API-Key.

Example: WhatsApp message via WaNotifier

Goal: send a WhatsApp message on every booking. Full WaNotifier guide including API key: WaNotifier (WhatsApp).

WaNotifier — Zapier: create a Zap (official)

1. Zap as in Option A: Catch Hook trigger ← MeetFlow webhook.
2. Action: app WaNotifier → on first use «Connect to Zapier» appears — paste API key from WaNotifier (see find API key).
3. Choose «Send Message Template (Via a Notification)».
4. Map recipient number, transactional notification, template variables from booking fields.
5. Test action → check WhatsApp → publish the Zap.

WhatsApp: WaNotifier/Zapier or direct via Meta?

For WhatsApp booking reminders there are two independent paths — you do not need both.

Meta — WhatsApp Cloud API WaNotifier — Zapier integration

1) Find your WaNotifier API key (for Zapier «Connect to Zapier» popup)

When you add a WaNotifier action in Zapier, a popup «Connect to Zapier» appears with «Enter API Key (required)». This key comes from your WaNotifier account — not from MeetFlow.

Optional: Add New Key — create a dedicated key for Zapier only.

Back in Zapier: paste the key → Connect. Zapier verifies and confirms the connection.

2) Create a transactional notification in WaNotifier

Before mapping in Zapier — without this notification the Zapier field Transactional Notification stays empty («No options are available»).

1. WaNotifier: Notifications → Add New (not «Broadcast» or «Marketing»).
2. Name: e.g. «MeetFlow New Booking».
3. Type: exactly Transactional / Integration / API (other types won't appear in Zapier).
4. Trigger: API request to a Webhook URL.
5. Message Template: pick an approved utility template.
6. Webhook Request Data: Default (for Zapier «Send Message Template»).
7. Save — status must show On-going.

Back in Zapier: open WaNotifier action → account ⋯ → Reconnect or reload the step → open Transactional Notification again.

Still empty? → Troubleshooting «No options available»

3) Zap: MeetFlow → WaNotifier

1. Trigger: Webhooks by Zapier → Catch Hook ← MeetFlow webhook URL (see Zapier).
2. Action: WaNotifier → Send Message Template (Via a Notification).
3. First time: connect WaNotifier (API key from step 1).
4. Map fields: recipient number, transactional notification, body variables from booking.
5. Test Step → check WhatsApp → Publish.

Option A — Instant trigger (Webhook node, recommended)

1. In n8n: create a new workflow → add a Webhook node as the trigger.
2. HTTP Method: POST · Path: e.g. meetflow-booking (your choice).
3. Activate the workflow → copy the production URL (e.g. https://your-n8n.example.com/webhook/meetflow-booking).
4. In MeetFlow: paste into Settings → Integrations → Webhook URLs → enable «Booking created» → save.
5. Click «Send test webhook» in MeetFlow → check execution log in n8n.
6. Add more nodes: e.g. Slack, Gmail, HTTP Request (WaNotifier), Google Sheets.
7. Map fields from the webhook body: {{ $json.booking.customer_name }}, {{ $json.booking.booking_date }}, {{ $json.booking.booking_time }}, {{ $json.booking.meeting_url }} …
8. Make a real test booking → verify execution in n8n.

Option B — Polling (Schedule + HTTP Request)

Requires the Scale plan. See Automation API.

1. Trigger: Schedule Trigger (e.g. every 5 minutes).
2. HTTP Request node:
   • Method: GET
   • URL: https://your-site.com/wp-json/meetflow/v1/integrations/bookings
   • Query: since = last run (ISO timestamp), limit = 25
   • Header: X-MeetFlow-API-Key = key from MeetFlow Integrations
3. Split In Batches or Loop over the bookings array → run action per booking.

Example: WhatsApp via WaNotifier

1. Webhook trigger as in Option A.
2. HTTP Request node → WaNotifier API (template message) or WaNotifier community node if installed.
3. Recipient: fixed number or {{ $json.booking.customer_phone }} (with country code).

Issues? → Troubleshooting Integrations

Option A — Instant trigger (Custom webhook, recommended)

1. In Make: new scenario → module Webhooks → Custom webhook as trigger.
2. Create webhook → copy the URL (format https://hook.eu1.make.com/… or US region).
3. In MeetFlow: paste into Settings → Integrations → Webhook URLs → enable «Booking created» → save.
4. Click «Send test webhook» in MeetFlow → in Make click «Determine data structure» / «Redetermine» — Make detects the JSON fields.
5. Add modules: e.g. Gmail, Slack, Google Sheets, HTTP (WaNotifier).
6. Map fields: booking.customer_name, booking.booking_date, booking.booking_time, booking.meeting_url …
7. Activate the scenario (toggle ON) → make a real test booking.

Option B — Polling (Schedule + HTTP)

Requires the Scale plan. See Automation API.

1. Trigger: Schedule (interval e.g. 5 minutes).
2. Module HTTP → Make a request:
   • URL: https://your-site.com/wp-json/meetflow/v1/integrations/bookings?limit=25&since=…
   • Method: GET
   • Header: X-MeetFlow-API-Key = key from MeetFlow
3. Iterator over the bookings array → run action per entry.

Example: WhatsApp via WaNotifier

1. Custom webhook as in Option A.
2. Module WaNotifier (if in Make catalog) or HTTP → Make a request to WaNotifier API.
3. Fill template variables from booking fields — always use an approved WhatsApp template.

Issues? → Troubleshooting Integrations