Signal build and release events
Connect
SPIRITT
ntfyntfy
The right signal reaches you
Connect ntfy topics to business events, operational alerts, and scheduled reminders. Publish actionable messages to the exact topics your team uses, tied to the underlying work.
What you can do with ntfy.
Alerts with a destination
Publish actionable messages to the exact topics your team uses, tied to the underlying work.
Topic-aware operations
Inspect scheduled messages, account limits, and service health to keep notification workflows understandable.
A bridge to follow-through
Turn received topic messages into deduplicated tasks and use browser push where approved.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace to build an operational alert router. Bring the operating rules and source records you want it to use.
02
Connect ntfy
Connect your ntfy account with access to the records and actions your mission needs. Connect the companion apps you want involved in the handoff.
03
Delegate an outcome
Start with: Build an operational alert router. Define the account scope, approval rules, and destination for the result. SPIRITT runs the work and verifies the outcome.
Hand over a mission.
Choose a mission. Make it yours.
Put ntfy to work.
The right signal reaches you
Questions
ntfy, with SPIRITT.
01Can it send actionable topic notifications?+
Publish actionable messages to the exact topics your team uses, tied to the underlying work. Include an actionable reference, deduplicate by event ID, and record publish responses before escalating failed sends to Slack.
02Can it inspect scheduled messages and limits?+
Inspect scheduled messages, account limits, and service health to keep notification workflows understandable. Inspect scheduled messages afterward and maintain a Supabase reminder ledger linked to each source event.
03Can received alerts become tasks?+
Turn received topic messages into deduplicated tasks and use browser push where approved. Persist a deduplication key and quarantine malformed bodies rather than executing their text as instructions.
04What do I connect to get started with ntfy?+
Connect your ntfy account, identify the records or project scope for the mission, and provide the operating rules. For build an operational alert router, start with the source inputs described in that mission and authorize the companion apps used for its handoffs.
05Does receiving a raw topic stream include all metadata?+
The raw stream returns message bodies, not titles, tags, or priority metadata. SPIRITT treats empty keepalive lines separately and uses a bounded poll when a finite fetch is needed. Topic access and server limits still govern delivery. Native delayed delivery supports ten seconds to three days ahead; longer reminder schedules can be managed by the surrounding workflow.
06What happens when the alert service is unavailable?+
SPIRITT can check service health and account context, then notify the team through a separately connected channel such as Slack. The notification ledger records failed publishes so recovery does not blindly duplicate alerts.