Skip to main content
By the end of this page you’ll have:

Skills installed

All four SuprSend skills active in your AI agent.

Workflow generated

A real cart-abandonment workflow built by AI from a single prompt.

Workflow live

That workflow pushed to your SuprSend workspace and ready to fire.
You’ll need Node.js 18+ and a SuprSend service token.
1

Install the skills

Run this in your project folder:
The installer detects which agents you have (Cursor, Claude Code, Copilot, etc.), asks which to install into, and lets you choose where the files land.
Committed to your repo, shared with your team. Recommended.
Pick this option and commit the skills folder. Your whole team gets identical agent behavior with zero extra setup.
After install, skills are passive - nothing extra to run. Open your agent and start describing what you want.
2

Generate a workflow with a single prompt

Open your agent (in Cursor, hit Cmd+L / Ctrl+L) and paste:
Your agent will say something like “I’ll use the suprsend-workflow-schema skill” and create a new file at suprsend/workflows/cart-abandonment/workflow.json containing valid workflow JSON - correct node_type values, a properly nested branch structure, and the exact field names the SuprSend schema expects.
If your agent doesn’t mention loading the skill, paste the prompt again and add “use the suprsend-workflow-schema skill” - some agents need an explicit nudge the first time.
Sanity-check the outputOpen suprsend/workflows/cart-abandonment/workflow.json and verify:
  • slug is set to cart-abandonment
  • A delay node sits before the delivery nodes
  • Each delivery node uses the correct node_type (send_email, send_inbox, etc.)
  • Any branch_waituntil conditions match your intent - agents are most likely to misfire here
3

Push it live

Confirm you’re pointed at the right workspace, then push:
Without --commit=true, the workflow is pushed as a draft and won’t fire. This catches almost everyone the first time.
Open app.suprsend.com → Workflows. Your workflow is live.

​
Common gotchas

These are the mistakes agents (and humans) make most often.
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/).
Why: Pushed workflows are drafts by default.Fix: Add --commit=true.
Why: Wrong active profile or workspace.Fix: Run suprsend profile list and switch with suprsend profile use --name <name>.
Why: The CLI takes the slug from the directory name, suprsend/workflows/<slug>/workflow.json, not from a field in the file. A slug inside the JSON that differs from the directory is replaced by the directory name.Fix: Save the file as suprsend/workflows/your-slug/workflow.json.
Why: Referenced schema or category doesn’t exist yet.Fix: Push schema and category first.
Why: Incorrect expression_v1 conditions.Fix: Review by hand. See Wait Until.

​
Next steps

Workflow Schema skill

All workflow nodes, fields, and the prompts that work best.

Template Schema skill

Author template variants across all nine channels from plain English.

CLI skill

Ask your agent to push, sync, generate types, and more.

Docs & Support skill

Let your agent fetch live SuprSend docs to answer questions.