If you already use IFTTT or Zapier as your home automation glue, MathNet plugs right in.
IFTTT
- Create an applet with Webhooks (the “IFTTT Maker” service) as the trigger
- Set the event name (e.g.
mathnet_redeem) - Get the trigger URL from your Webhooks settings — it looks like:
https://maker.ifttt.com/trigger/mathnet_redeem/with/key/YOUR_KEY
- Paste that URL into MathNet’s Webhook URL field
- Wire up any IFTTT action — log to Google Sheets, email yourself, post a tweet, toggle a Philips Hue light, etc.
IFTTT’s Webhooks trigger exposes the JSON body’s fields as Value1/Value2/Value3 if you want to interpolate the device name or balance into your action.
Zapier
Zapier’s Webhooks by Zapier “Catch Hook” trigger gives you a unique URL:
https://hooks.zapier.com/hooks/catch/YOUR_ID/YOUR_HOOK/
Paste that URL into MathNet. Zapier auto-parses the JSON body and exposes all fields (event, credits, balance_after, device_name, timestamp) as variables for the rest of your Zap.
Common Zap recipes:
- Log every redemption to a Google Sheet — running tally for end-of-month allowance
- Email weekly summary — Zapier’s “Digest” + Email steps work well here
- Update a Notion database — track family chore/learning progress in one place
- Cross-post to multiple services — send the same redemption to Pushover and Discord and a spreadsheet
Which to pick?
- IFTTT — simpler, one trigger → one action. IFTTT Free now caps active applets at 2; anything beyond that needs IFTTT Pro (paid). For a single redemption webhook this is usually fine.
- Zapier — multi-step zaps, filters, paths, formatters; more flexibility but you’ll outgrow the free tier (100 tasks/month, single-step zaps) fast if redemptions happen daily.
If you only want one notification per redeem, IFTTT is easier. If you want to fan out to multiple destinations or apply logic, Zapier earns its keep.