Drag-and-drop scenarios
Each Make scenario is a flowchart. Add modules, connect them, click run. No code, no scripting, no terminal.
Make.com is the visual cousin of Zapier. Connect Getwello and you can build branching scenarios that route check-ins, missed-day alerts and Family Room messages into dozens of destinations, all without writing a line of code.
Coordinator-only. Included in the £4.99 plan. Same day to set up.
Each Make scenario is a flowchart. Add modules, connect them, click run. No code, no scripting, no terminal.
Conditional routing, loops over arrays, batch aggregation. The kind of logic that's awkward in Zapier is native in Make.
1,000 free ops/month. Paid plans roughly half the cost of Zapier's equivalent. Friendly to multi-integration families.
Gmail, Sheets, Notion, Airtable, Discord, Telegram, SMS, your CRM. If Make has a module for it, you can route Getwello events there.
A Make scenario is a single canvas you can take in at a glance. Drop a webhook, add a router, drop in the destinations. The whole family wiring is one diagram you can show a sibling and they will get it.
Settings → Developer API as a Coordinator. Name it 'Make.com'. Copy the gw_live_ token.
In Make, create a scenario, add a Webhooks → Custom webhook module. Make gives you a URL; copy it.
Settings → Developer API → Webhooks. URL is the Make webhook from step 2. Tick the events you want this scenario to fire on.
Add a Router for branching, then any combination of destination modules. Click Run once. When the test event arrives, map fields. Turn the scenario on.
Make uses a visual scenario builder rather than linear Zaps, supports iteration and aggregation natively, and is generally cheaper for high-volume use. Make is stronger on multi-step branching; Zapier is simpler for one-step flows.
The free tier covers 1,000 operations a month, which is plenty for a typical family Circle. Paid plans start at around £8/month if you scale to many integrations or trigger frequencies.
Yes, using the HMAC SHA-256 module. Drop it in after the webhook trigger, configure with the signing secret you copied at subscription create, reject anything that doesn't match. Documented in our setup guide.
Iterators (loop over arrays inside a single scenario), aggregators (collect multiple events into one batch), and proper error-handling branches. Useful for Getwello scenarios that fan out to several destinations conditionally.
There's no automatic import. The pattern is the same: webhook trigger from Getwello, the destination modules you already know. Migration is mostly a few hours of recreating the visual scenarios.
Some families wire two or three at the same time. The webhook fans out, the API keys stay the same.
See every integration or jump to the Developer API overview.
Mint your first API key in two minutes. Coordinator-only. Included in the £4.99 family plan.