Zapier
Zapier is the universal pivot — any event from 7000+ supported apps can fan out to Splashify with a single Zap step. No signing scheme (Zapier sends raw payloads); use the unique URL as your shared secret.
Setup
1. Copy the Splashify webhook URL
Integrations → Zapier in Splashify → copy:
https://apis.splashifypro.com/api/v1/webhooks/integrations/<your-user-id>/zapier2. Build the Zap
zapier.com → Create Zap.
-
Trigger — pick any trigger app and event (e.g. New row in Google Sheets, New lead in Facebook Ads, New issue in GitHub).
-
Action — Webhooks by Zapier → Custom Request.
-
Configure:
Field Value Method POST URL URL from step 1 Data Pass-Through? No Data JSON object mapping fields you want in Splashify. Example: { "phone": "{{phone_from_trigger}}", "first_name": "{{first_name_from_trigger}}", "amount": "{{amount_from_trigger}}", "order_id": "{{id_from_trigger}}" }Field Value Unflatten Yes Headers Content-Type: application/jsonBasic Auth (leave empty) -
Test Step — Zapier fires a test request to Splashify. Keep that tab open.
3. Configure the integration in Splashify
Configuration tab:
- Phone Field →
phone(or whatever key you used in the Zap’s JSON body) - Variables → map
{{1}}tofirst_name,{{2}}toamount, etc. - Toggle Enabled → Save.
4. Publish the Zap
Zapier → Publish. Going forward every matching trigger event fires your WhatsApp template.
Use cases
- Typeform submission → welcome message — New form response → Splashify welcome template
- Stripe payment in a different Stripe account — If you have multi-account setups, one Stripe → Zapier → Splashify keeps the split clean without setting up our first-class Stripe integration
- Google Sheets → reminder — Add a row with phone + message → Splashify fires the template
Gotchas
- Zapier’s free tier rate-limits you. If you expect > 100 events/day, move to Pabbly Connect or Make for unlimited tasks.
- JSON shape is yours to design. Structure it to match Splashify’s variable mapping — flat keys like
phone,name,amountwork best. - No event routing. Every Zap-fired request is treated identically; use multiple integration slugs (one per scenario) if you need different templates per event type.