What is SuprSend?

• Developers trigger workflows from one API call or event, keep workflows and templates in Git, and promote them from staging to production.
• Product teams design workflows, templates and the preference center, and change copy or logic without a code deploy.
• Growth and marketing teams send broadcasts to SQL segments (beta) and track results across channels in analytics.
• AI agents can do any of this for any team. They build, test and debug notifications through the MCP server and Agent Skills, with your role’s permissions. Your own production agents send notifications through the Agent SDK (early access).

​

Get started

​

How SuprSend works

1. Trigger. Your backend calls the workflow API or sends an event. A workflow can also start when a user joins or leaves a list, and a broadcast sends one message to a whole list.
2. Preference check. SuprSend skips users who opted out of the category or channel, before the workflow runs and again at each send step. See preference evaluation.
3. Workflow. A workflow can delay, batch, digest or branch. It can also wait until something happens, send only in a time window in the user’s timezone, throttle how often a user gets it, fetch data from your API or invoke another workflow.
4. Send step. Each send step picks the channels, the template, the translation and any variant for the customer or condition. Content changes don’t need a code deploy.
5. Delivery. SuprSend sends through your own providers (SuprSend calls them vendors), such as SendGrid, Amazon SES, Twilio, Firebase Cloud Messaging and APNs, and reroutes to a fallback provider if one fails.
6. Logs. Follow every request, workflow run and message in logs, including messages that were skipped and why. Track results in analytics, or send status events to your systems with webhooks.

curl --request POST \
  --url https://hub.suprsend.com/trigger/ \
  --header "Authorization: Bearer __YOUR_API_KEY__" \
  --header 'Content-Type: application/json' \
  --data '{
    "workflow": "order-shipped-notification",
    "recipients": [{ "distinct_id": "user_1a2b3c" }],
    "data": { "order_id": "ORD-1234" }
  }'

const { Suprsend, WorkflowTriggerRequest } = require("@suprsend/node-sdk");
const supr_client = new Suprsend("_workspace_key_", "_workspace_secret_");

const w1 = new WorkflowTriggerRequest({
  workflow: "order-shipped-notification",
  recipients: [{ distinct_id: "user_1a2b3c" }],
  data: { order_id: "ORD-1234" },
});

supr_client.workflows.trigger(w1).then((res) => console.log(res));

from suprsend import Suprsend, WorkflowTriggerRequest

supr_client = Suprsend("_workspace_key_", "_workspace_secret_")

w1 = WorkflowTriggerRequest(body={
    "workflow": "order-shipped-notification",
    "recipients": [{"distinct_id": "user_1a2b3c"}],
    "data": {"order_id": "ORD-1234"},
})

res = supr_client.workflows.trigger(w1)

​

Core concepts

​

What you can build

• Sign-in codes and security alerts that users can’t opt out of, sent by SMS or WhatsApp with a fallback provider.
• Activity alerts that don’t flood users. Batch many comments or updates into one message, or send a daily or weekly digest.
• An in-app notification feed with the Inbox, plus a preference center where users choose what they get.
• Alerts for each of your business customers, with their branding, their providers and their admin’s defaults, using tenants.
• Campaigns and announcements to a list or SQL segment (beta), across email, push, WhatsApp and inbox.
• Messages from your own AI agents, which call your workflows as tools through the Agent SDK (early access).

​

Built API-first

• Every core object has an API. Users, objects, tenants, lists, workflows, templates, preferences and translations all have APIs. See the API reference and the Management API.
• Notifications as code. Pull and push workflows and templates with the CLI, keep them in Git, and sync them from staging to production. Validate trigger payloads with JSON Schema and generate types from them.
• Agent-ready by design. The MCP server exposes the same objects as tools, and agents act with your account’s permissions.

​

For product and growth teams

• Change content in each channel’s editor, and preview and test it before it goes live. See templates.
• Send campaigns to a list as a broadcast, now or on a schedule.
• Build audiences with a SQL segment (beta) that the AI agent can write for you, or from a database sync, a CSV or Mixpanel.
• Let users choose what they receive with a hosted or embedded preference center.
• See results by channel, workflow and category in analytics.
• Ask questions in plain English about delivery and engagement through the SuprSend Agent or the Slack Agent.

​

For products that serve other businesses

• Tenants hold each customer’s branding, preferences and providers. They’re available on the Enterprise plan and as an add-on for the Business plan.
• Sub-tenants nest up to 5 levels, and a child inherits its parent’s preferences, vendors, branding and properties.
• Tenant preferences let a customer’s admin set defaults for their own users.
• Tenant providers send through your customer’s own email or SMS accounts.
• Objects represent teams, projects or channels that people subscribe to, so you notify the group instead of listing every member.
• Slack and Microsoft Teams messages can go into your customers’ own workspaces.

​

For AI agents: MCP server, Agent Skills and Agent SDK

• Agents that operate SuprSend. The hosted MCP server (beta) gives AI clients such as Claude, ChatGPT, Codex, Cursor, Gemini and VS Code access to your workspace. Agents can debug why a user didn’t get a message, query analytics, and edit workflows and templates as drafts before publishing. They sign in with your SuprSend account and can’t do more than your role allows. Agent Skills (beta) give coding agents SuprSend’s schemas, CLI flags and examples, so they work from the real spec instead of guessing. The Agent plugin adds both to Claude Code, VS Code, Codex and Cursor in one install.
• Agents that send notifications. The Agent SDK (beta, early access) turns your workflows into schema-checked tools that production agents can call when they need to tell a person something.
• Docs agents can read. Every page is available as Markdown by adding .md to its URL. llms.txt lists every page, and llms-full.txt holds the whole site in one file.

​

Security, reliability and deployment