SpecsModelExploreRequirements
SpecsModelExploreRequirements
Notification Provider
Overview
Guide
Twin streams
Links and Communications
IDexternal_systems.notification_provider
DescriptionPush / SMS provider for device alerts.
Keynotification_provider
Typeexternal
Statusactive
TechnologiesTwilio, FCM, APNs, Webhooks
Tags
Table of contents
Guide
Notification Provider
Channels
Failure handling
Where it sits in the flow
Links and Communications
Requirements

Attributes

channelsSMS, Push, Webhook
directionoutbound

Guide

Notification Provider

The Notification Provider is the third-party delivery layer that turns an alert into something a human actually receives — a push notification, an SMS, or a webhook to another system. We hand off the message; they handle the last mile.

Integration contract

Outbound only. The platform calls provider APIs (Twilio, FCM, APNs, Webhooks) with a rendered message and a target; delivery receipts come back asynchronously.

Channels

Push

FCM (Android) and APNs (iOS) for in-app and lock-screen alerts.

SMS

Twilio for high-urgency, app-independent reach.

Webhook

HTTP callbacks for integrating with customer-side systems.

Failure handling

  • Provider errors are retried with backoff; hard failures fall back to an alternate channel where configured.
  • Delivery is at-least-once — consumers dedupe on alert id.
  • A provider outage degrades notifications only; alert evaluation continues upstream and backfills once delivery recovers.

Where it sits in the flow

The provider is the final hop of the alert pipeline:

Links and Communications

1 incoming link · 1 workflow

Incoming Links(1)

Source objectLabelLink typeRelationRaw idRequiredDescription
Mobile App

example-iot.product.user_facing.mobile_app

microservice:app
receives push from—linksexternal_systems.notification_provider——

Related Workflows(1)

WorkflowModelParticipant idParticipant label
Telemetry to alert

telemetry.alert-pipeline

example-iotexternal_systems.notification_providerNotifications

Requirements