--slug vs --dir, or whether --commit=true is needed.
The skill loads the full SuprSend CLI reference into your agent’s context: every command, every flag, and the gotchas that catch people most.
Install
Full CLI Reference
Try it
1
Ask your agent
2
Your agent runs the right command
Successfully pushed: 0.Things you can ask your AI to do
Push and version a workflow
Push and version a workflow
“Push the onboarding workflow as a draft, then commit it once I confirm.”Your agent will push without
--commit=true first, wait for your sign-off, then run a follow-up commit.Pull, edit, push
Pull, edit, push
“Pull the password-reset workflow from production, change the SMS delay from 5 minutes to 2, and push the change to staging.”Full lifecycle - pull, modify locally, push back - handled by the agent.
Sync between workspaces
Sync between workspaces
“Sync all workflows and schemas from staging to production.”The agent runs
suprsend sync with the right --from, --to, and --assets flags (for example suprsend sync --from staging --to production --assets workflow).Generate type-safe SDK code
Generate type-safe SDK code
“Generate TypeScript types for all my event schemas into ./types.”The agent runs
suprsend generate-types <language> for TypeScript, Python, Go, Java, Kotlin, Swift, or Dart (for example suprsend generate-types typescript --output-file ./types/suprsend-types.ts).Set up CI/CD
Set up CI/CD
“Add a GitHub Actions step that pushes any changed workflows on merge to main.”The agent generates the workflow YAML using the right CLI commands and environment variables.
Manage schemas, events, categories, translations
Manage schemas, events, categories, translations
“Push every event schema in ./schemas to staging.”Works for schemas, events, preference categories, and translations - same patterns as workflows.
For AI-agent access to SuprSend (users, workflows, templates, broadcasts, delivery analytics), use the hosted SuprSend MCP server at
https://mcp.suprsend.com/mcp. Sign in with your SuprSend account — no CLI or service token needed.Before your first command
The CLI needs a service token. Pick the auth flow that fits your setup:- Environment variable
- Saved profile
Common gotchas
These are the mistakes the skill is built to prevent - but worth knowing if something looks off.workflow push myfile.json fails with "failed to read workflow file"
workflow push myfile.json fails with "failed to read workflow file"
Why: The positional argument is a workflow slug, not a file path. The command reads
suprsend/workflows/<slug>/workflow.json.Fix: Pass the slug (suprsend workflow push cart-abandonment or --slug cart-abandonment), or point --dir at a directory with the <slug>/workflow.json layout (default suprsend/workflows/).Workflow pushed but nothing fires
Workflow pushed but nothing fires
Why: Pushed workflows are drafts by default.Fix: Add
--commit=true."Successfully pushed: 0"
"Successfully pushed: 0"
Why: Wrong active profile or workspace.Fix: Run
suprsend profile list and switch.Validation error on push
Validation error on push
Why: Referenced schema or category doesn’t exist.Fix: Push dependencies first.