suprsend-cli skill gives your agent the complete SuprSend CLI reference so it can run commands correctly on the first try — no guessing at flags or subcommand names.
Installation
What it enables
Full workflow lifecycle
Pull workflows from your workspace, edit locally, and push back — with
--commit=true and --commit-message for version tracking.Multi-asset management
Manage not just workflows but also schemas, events, preference categories, and translations — all from the terminal.
Cross-workspace sync
Sync notification assets between staging and production workspaces in a single command.
Type generation
Generate TypeScript, Python, Go, Java, Ruby, Swift, or Kotlin type definitions from your event schemas for type-safe integrations.
CI/CD pipelines
Configure GitHub Actions, GitLab CI, or other pipelines to pull, validate, and push notification changes automatically on merge.
Start MCP server
Start and configure the SuprSend MCP server directly from the terminal with
suprsend start-mcp-server.Before using the CLI
All commands require a service token. Set it as an environment variable:--workspace switches between workspaces within an account. The profile command is for self-hosted or BYOC deployments. See Setting Up CLI Access.Example commands
Common gotchas
| What goes wrong | Why | Fix |
|---|---|---|
workflow push myfile.json silently pushes 0 | Command expects --slug or --dir, not a file path | Use --slug or --dir suprsend/workflow/ |
| Workflow pushed but nothing fires | Pushed workflows are drafts by default | Add --commit=true |
| ”Successfully pushed: 0” | Wrong active profile or workspace | Run suprsend profile list and switch |
| Validation error on push | Referenced schema or category doesn’t exist | Push dependencies first |
Learn more
Runsuprsend --help or suprsend <command> --help for full flag details.
Full CLI Reference
Every command, subcommand, flag, and output format.
suprsend-workflow-schema
Generate valid workflow JSON to push.