# Build or edit a notification workflow from an agent (slim)

> 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.

- Full: https://www.anchorterminal.com/niches/notifications.build-workflow/index.md (~1,100 tokens) · this version ~280 tokens · JSON https://www.anchorterminal.com/niches/notifications.build-workflow/index.json · canonical https://www.anchorterminal.com/niches/notifications.build-workflow/
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-15
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Two or three companies' docs show a full fit. Full fit: 2 companies, with a limit: 5, tagged: 8. Weight 6, 1 accounts.

Done when: 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.
yes: knock (Knock Labs, Inc.)
yes: suprsend (SuprStack Inc)
caveat: courier (trycourier.com, Inc.)
caveat: magicbell (MagicBell, Inc.)
caveat: novu (Noti-Fire Apps Ltd.)
caveat: onesignal (OneSignal, Inc.)
caveat: pingram (Pingram)

Data: https://www.anchorterminal.com/api/v1/use-cases/notifications.build-workflow.json
