Service
IFTTT Webhooks — trigger an IFTTT applet via a simple HTTP POST, fanning a notification out to whatever IFTTT is chained to (SMS, smart home, other apps). One of the oldest "generic trigger" integrations still commonly used to bridge self-hosted alerts into consumer ecosystems.
Why now
Included as the legacy end of this batch — an older but still-active integration point some self-hosters keep around for reaching non-technical family members or smart-home routines, per the task's ask to work from newest favorites down to legacy/older services.
Apprise comparison
Apprise supports IFTTT (ifttt://) — a gap versus Apprise's coverage today.
Proposed scope
This is close to providers/webhook (generic JSON POST) rather than needing a bespoke shape:
providers/ifttt packageConfig{ WebhookKey, EventName }New(cfg, wrapper) *Client, (*Client).Send(ctx, notify.Message) error via transport.Wrapper
Note
Per CLAUDE.md, this repo's near-term policy is to keep the provider list to what's ported from Charon and not add new integrations without an explicit go-ahead. This issue is tracking/backlog only — do not implement without maintainer sign-off.
Service
IFTTT Webhooks — trigger an IFTTT applet via a simple HTTP POST, fanning a notification out to whatever IFTTT is chained to (SMS, smart home, other apps). One of the oldest "generic trigger" integrations still commonly used to bridge self-hosted alerts into consumer ecosystems.
Why now
Included as the legacy end of this batch — an older but still-active integration point some self-hosters keep around for reaching non-technical family members or smart-home routines, per the task's ask to work from newest favorites down to legacy/older services.
Apprise comparison
Apprise supports IFTTT (
ifttt://) — a gap versus Apprise's coverage today.Proposed scope
This is close to
providers/webhook(generic JSON POST) rather than needing a bespoke shape:providers/iftttpackageConfig{ WebhookKey, EventName }New(cfg, wrapper) *Client,(*Client).Send(ctx, notify.Message) errorviatransport.WrapperNote
Per
CLAUDE.md, this repo's near-term policy is to keep the provider list to what's ported from Charon and not add new integrations without an explicit go-ahead. This issue is tracking/backlog only — do not implement without maintainer sign-off.