notiflows.com valid
Notiflows
Notification infrastructure for SaaS products. Model a notiflow once and deliver it across in-app, email, SMS, mobile push, web push, chat, and webhooks from a single API.
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T17:54:44.844Z. Cached copy · Source on notiflows.com
# Notiflows
> Notification infrastructure for SaaS products. Model a notiflow once and deliver it across in-app, email, SMS, mobile push, web push, chat, and webhooks from a single API.
A notiflow is the orchestration unit of the platform: a structured sequence of steps that decides which notifications go out, on which channels, and under what conditions. Teams design notiflows in a visual builder or as versioned JSON, then trigger them from a server-to-server API. The platform handles per-user preferences, digesting, throttling, provider failover, and a real-time in-app inbox. Notiflows can also be managed as code through a CLI, an MCP server, and an agent toolkit.
- [Documentation home](https://notiflows.com/docs): Entry point for all guides and the API reference
## Getting Started
- [Quick Start](https://notiflows.com/docs/getting-started/quick-start): Send your first notification with Notiflows in minutes
- [What is Notiflows?](https://notiflows.com/docs/getting-started/what-is-notiflows): Learn what Notiflows is and what it can do for you
## Concepts
- [Broadcasts](https://notiflows.com/docs/concepts/broadcasts): Send notifications to everyone subscribed to a topic
- [Channel Settings](https://notiflows.com/docs/concepts/channel-settings): Storing recipient-specific data for channels like device tokens and chat connections
- [Channel Subscriptions](https://notiflows.com/docs/concepts/channel-subscriptions): Managing per-device push subscriptions for web push and other subscription-based channels
- [Channels](https://notiflows.com/docs/concepts/channels): Learn about notification channels
- [Deliveries](https://notiflows.com/docs/concepts/deliveries): Learn about notification deliveries
- [Notifications](https://notiflows.com/docs/concepts/notifications): Understanding notifications
- [Notiflows](https://notiflows.com/docs/concepts/notiflows): Understanding Notiflows
- [Preferences](https://notiflows.com/docs/concepts/preferences): Learn about user preferences
- [Subscriptions](https://notiflows.com/docs/concepts/subscriptions): Understanding subscriptions
- [Users](https://notiflows.com/docs/concepts/users): Understanding users in Notiflows
## Channels & Providers
- [Channels Providers overview](https://notiflows.com/docs/channels-providers): Channels and providers in Notiflows
- [Browser Push overview](https://notiflows.com/docs/channels-providers/browser-push): Web push notifications
- [Discord](https://notiflows.com/docs/channels-providers/chat/discord): Configure Discord as a chat provider in Notiflows
- [Chat overview](https://notiflows.com/docs/channels-providers/chat): Send notifications to chat platforms
- [Slack](https://notiflows.com/docs/channels-providers/chat/slack): Configure Slack as a chat provider in Notiflows
- [Telegram](https://notiflows.com/docs/channels-providers/chat/telegram): Configure Telegram as a chat provider in Notiflows
- [WhatsApp](https://notiflows.com/docs/channels-providers/chat/whatsapp): Configur
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| suprsend.com | www.suprsend.com llms.txt | interface Developer tools APIs and SDKs +1 | US | 58 | ✓ | ✓ | |
| novu.co | Novu | interface AI and machine learning Communications +2 | US | 53 | ✓ | ||
| pushalert.co | PushAlert | interface Marketing Ecommerce +1 | US | 54 | ✓ | ||
| notifuse.com | Notifuse Documentation | documentation Communications Marketing +1 | US | 46 | ✓ | ✓ | |
| notis.ai | Notis | interface AI agents and MCP Developer tools | US | 52 | ✓ | ||
| smsapi.com | SMSAPI | interface Communications APIs and SDKs +1 | PL | 55 | ✓ | ||
| senderkit.com | SenderKit | interface Developer tools Communications +1 | — | 46 | ✓ | ✓ | |
| pushwoosh.com | Pushwoosh | documentation Data and analytics Marketing +1 | FI | 69 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=notiflows.com · GET /v1/domain/notiflows.com · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage notiflows.com, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for notiflows.com:
1. POST https://agentwebmap.com/v1/sites/notiflows.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://notiflows.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/notiflows.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/notiflows.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.