# Build or edit a notification workflow from an agent

> Build or edit a notification workflow from an agent: 2 companies fully do it, 5 with a limit, 8 carry the tag. Every listing in Notifications with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/notifications.build-workflow/
- Markdown: https://www.anchorterminal.com/niches/notifications.build-workflow/index.md (~1,100 tokens)
- Slim: https://www.anchorterminal.com/niches/notifications.build-workflow/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/notifications.build-workflow/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 5 | 8 | 6 | 1 |

## What counts as done

The workflow, its templates and channel steps are created or changed through an API, CLI or MCP tool, committed in a development environment and readable back, without the dashboard; a read-only mode or tool filter exists for inspection.

How agents ask for it: set up a welcome notification workflow; add an SMS step to this workflow; why did this workflow skip the email

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Knock (Knock Labs, Inc.)**: CLI pulls and pushes workflows and templates as files, validates, commits and promotes between environments; the MCP server builds workflows and a session without Manage resources is read-only.
- **SuprSend (SuprStack Inc)**: Management API creates, updates and commits workflows and templates, the CLI syncs workspaces, and the hosted MCP keeps edits as drafts until published, with a ?tools= filter to load only read groups.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Courier (trycourier.com, Inc.)**: Templates have a create, draft and publish API manageable from Git, the CLI or MCP, and journeys build as JSON over the API, with Test and Production environments. The MCP server exposes 170 tools on a raw API key, with no filter or read-only mode documented.
- **MagicBell (MagicBell, Inc.)**: PUT /workflows saves a definition of steps with JMESPath conditions and GET reads it back, with run status by id. Project tokens are project-wide with no read-only mode, and no MCP server or environments were found.
- **Novu (Noti-Fire Apps Ltd.)**: Workflows API creates, updates, retrieves and syncs workflows between environments, and the hosted MCP manages them. MCP is Cloud only (acc-20), and keys have full rights with no read-only mode documented.
- **OneSignal (OneSignal, Inc.)**: The hosted MCP server includes Journey and template tools and checks app permissions, but it is OAuth-enabled per app, loads its full tool list, and no read-only mode or tool filter is documented.
- **Pingram (Pingram)**: Notification types and per-channel templates are managed by API and environments are listed, but no workflow steps exist beyond templates, and no read-only mode for the MCP connector was found.

- not this job: Amazon SNS (Amazon Web Services, Inc.): No workflow or template objects; topics and subscriptions only.
- not this job: Expo Push Notifications (650 Industries, Inc.): No workflow or template objects.
- not this job: Firebase Cloud Messaging (Google LLC): No workflow or template objects.
- not this job: ntfy (ntfy LLC): No workflow or template objects to build; each publish is self-contained.
- not this job: Pushover (Pushover, LLC): No workflow or template objects.

## What stops agents finishing

- MCP server hosted only, not in the self-hosted build
- management key with full rights and no read-only mode

## Around it

Before: code.read-repo. After: notifications.send-user-event.

## Where this comes from

Weight 6 of 100 in Notifications: 1 account (acc-20, Claude unable to find a self-hostable Novu MCP server); the rest rests on vendor pages for the Knock, Novu, Courier and SuprSend MCP servers and Knock's CLI

As data: https://www.anchorterminal.com/api/v1/use-cases/notifications.build-workflow.json, or the MCP tool get_use_case with id notifications.build-workflow. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
