Reaches the sibling who never installs apps
Slack is already on their laptop and phone. The Family Room conversation arrives there without negotiation.
Working parents and remote siblings already live in Slack. Mirror the Family Room into a private channel and Mum's check-ins, missed-day alerts and new visits land where you already look, no second tool to monitor.
Coordinator-only. Included in the £4.99 plan. Same day to set up.
Slack is already on their laptop and phone. The Family Room conversation arrives there without negotiation.
Mum's check-in lands next to your standup reminders. Same flow, no second app to monitor.
Years of Family Room conversations, indexed in the tool you already use. Threading, pins, search all work normally.
Incoming Webhooks take 30 seconds to create and cost nothing. Both ends are covered by what you already pay.
Mum taps her button. Within a second or two, a Getwello message appears in your Slack channel with the time, the mood, and a green tick. Everyone with the channel open sees it at once. No coordination, no chasing, no separate notification stack.
Suggested name: #family-getwello. Invite the people you want to see Mum's events. They do not need Getwello accounts to read the channel.
In Slack: Apps → Incoming Webhooks → Add to Slack. Pick the channel. Slack gives you a webhook URL that starts with hooks.slack.com.
https://hooks.slack.com/services/T0XXX/B0XXX/abc...Open Settings → Developer API as a Coordinator, scroll to Webhooks, paste the Slack URL, tick the events you want (suggest check_in.created plus check_in.missed for v1).
Our Test button fires a synthetic event. If your Slack channel shows a message within a couple of seconds, you're live. Tune the event list later by deleting and recreating the subscription.
Slack incoming webhooks accept a specific JSON shape. Our webhook fires the standard event JSON, which Slack displays as raw text by default. To get a nicely-formatted block-kit message, route through a small middleman (Zapier, a Cloudflare Worker or an n8n flow) that reshapes the payload. The setup guide has examples.
Not through the incoming webhook (that's one-way: Slack-in). For two-way, build a small Slack app using the Events API plus our POST /api/v1/family-room endpoint. Doable but more work; we suggest pinning that for v2 once one-way is working.
No. Anyone in the Slack channel sees the messages. If you want them to be Coordinators or Support Members in the Circle (with the proper role and audit trail), they'd need a Getwello account. For passive observers, the Slack channel alone is enough.
Yes, when creating the webhook subscription. The events checklist controls exactly which events fire. Only want missed-day alerts? Tick only check_in.missed. Easy to change later by deleting and recreating the subscription.
Almost identical setup. Teams supports incoming webhooks via Connectors. Same principle: create the Connector in Teams, paste the URL into Getwello webhook settings, done. A dedicated Teams page is on the roadmap.
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.