# Connect Flow to Zapier > To connect SkedX Flow and Zapier. Zapier → Flow: create an inbound hook in Flow (Settings → Developers → Inbound Hooks) that sends your approved template, then in the Zap add the action Webhooks by Zapier → POST with the hook’s address as the URL, Payload Type json, and your fields under Data; add the hook’s secret as a header before real traffic. Flow → Zapier: start a Zap with Webhooks by Zapier → Catch Hook, copy its URL into Flow’s Settings → Developers → Outbound Webhooks, choose the events, and trigger one so Zapier can see a sample. No API key or code is needed either way. Product: SkedX Flow · Topic: APIs & Developers · Draft — steps not yet re-verified in the live product Zapier connects thousands of apps. With Flow on one end, a new row in a sheet, a form entry or a payment can send a WhatsApp template — and a customer’s message in Flow can create a task or a row somewhere else. No code and no API key: Flow’s inbound hooks and outbound webhooks do the work. About ten minutes each way. ## Step 1: Zapier → Flow: make an inbound hook In Flow, create an [inbound hook](https://skode.ai/help/flow/developers/inbound-hooks-send-without-code/) whose action is **Send a WhatsApp template**. For the example, paste the fields your Zap will send — say `{"phone": "919876543210", "name": "Asha", "batch": "Batch 108"}` — and check the mapping (1–3). Create it and copy its address. ## Step 2: Add a “Webhooks by Zapier” step In your Zap, after the trigger (a new sheet row, a form entry…), add the action **Webhooks by Zapier** with the event **POST**. Paste the hook’s address into **URL**, set **Payload Type** to `json`, and under **Data** add one row per field — the same names you pasted in Flow, filled from your trigger. ## Step 3: Test without sending, then for real To test safely, first add `dry-run/` to the end of the URL and click **Test step**: Flow answers with what it would do and sends nothing (1–3). Then remove `dry-run/`, test again with your own number, and turn the Zap on. ## Step 4: Add a secret before real traffic Anyone with the address can call it, so make a new hook with **A secret word in a header**, and in Zapier’s **Headers** add `X-Flow-Secret` with that word. Set a daily cap too. [Secure an inbound hook](https://skode.ai/help/flow/developers/secure-an-inbound-hook/) has every option. ## Step 5: Flow → Zapier: catch Flow’s events Start a Zap with the trigger **Webhooks by Zapier** -> **Catch Hook** and copy the URL Zapier gives you. In Flow, open **Settings -> Developers -> Outbound Webhooks**, click **+ New webhook**, give it a name, paste Zapier’s URL under **Where should we send it?** and click **Create**; then open it and tick the events you want — for example A customer sends a message ([more on webhooks](https://skode.ai/help/flow/developers/outbound-webhooks/)). Make the event happen once (message your own number), then click **Test trigger** in Zapier to pick it up and map its fields. ## Common questions ### Do I need an API key for Zapier? No. Zapier -> Flow goes through an inbound hook, whose address is its credential; Flow -> Zapier goes through an outbound webhook. If you prefer to use the API directly, use **Custom Request** with the header `Authorization: Bearer sk_flow_…` — but store the key carefully. ### Does each Zap run cost anything in Flow? Each template Flow sends is charged to the messaging wallet at its category’s rate. Zapier counts tasks on its own plan. ### Zapier sent the data, but nothing arrived on WhatsApp. Open the hook in Flow’s Inbound Hooks list: **Recent calls** shows what arrived and why Flow did or didn’t send — a missing phone, a condition that didn’t match, the daily cap. The answer Zapier shows says the same. ### Can a Zap send different templates? One hook sends one template. Make one hook per template, or send through the API with **Custom Request**, where the template name is part of each request. ## Useful links - Inbound Hooks in Flow — Settings → Developers → Inbound Hooks: https://flow.skode.ai/settings/?tab=inbound_hooks - Zapier: Send webhooks in Zap workflows — the POST step, in Zapier’s own words: https://help.zapier.com/hc/en-us/articles/8496326446989 - Zapier: Trigger Zap workflows from webhooks — the Catch Hook trigger: https://help.zapier.com/hc/en-us/articles/8496288690317 Videos and screenshots © 2026 SkedX, with sample data only. Share and link to them freely; copying the SkedX product or its design is not allowed. Terms: https://skode.ai/terms/ ## Related guides - Send WhatsApp templates without code, using an inbound hook: https://skode.ai/help/flow/developers/inbound-hooks-send-without-code/ - Secure an inbound hook: https://skode.ai/help/flow/developers/secure-an-inbound-hook/ - Connect Flow to n8n: https://skode.ai/help/flow/developers/connect-flow-to-n8n/ - Get notified with outbound webhooks: https://skode.ai/help/flow/developers/outbound-webhooks/ Source: https://skode.ai/help/flow/developers/connect-flow-to-zapier/