Quickstart

Install SuprSend Agent Skills and ship your first AI-generated workflow in under 5 minutes.

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:

   npx skills add suprsend/skills
   

   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.

   Project-scoped (recommended)

   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.

   Global

   Available across every project on your machine. Pick this if you’re trying skills out solo.

   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:

   Create a SuprSend cart abandonment workflow JSON with slug
   "cart-abandonment". It should send 1 hour after the user
   leaves the cart, then send email and in-app notifications.
   

   Your agent will say something like “I’ll use the suprsend-workflow-schema skill” and create a new file at suprsend/workflow/cart-abandonment.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 output

   Open suprsend/workflow/cart-abandonment.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:

   suprsend profile list
   suprsend profile use --name my-workspace   # if needed
   suprsend workflow push --slug cart-abandonment --commit=true
   

   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.

workflow push myfile.json silently pushes 0

Why: The command expects --slug or --dir, not a file path.

Fix: Use --slug or --dir suprsend/workflow/.

Workflow pushed but nothing fires

Why: Pushed workflows are drafts by default.

Fix: Add --commit=true.

"Successfully pushed: 0"

Why: Wrong active profile or workspace.

Fix: Run suprsend profile list and switch with suprsend profile use --name <name>.

Workflow JSON can't be targeted by slug

Why: Missing slug field in the JSON.

Fix: Always include "slug": "your-slug".

Validation error on push

Why: Referenced schema or category doesn’t exist yet.

Fix: Push schema and category first.

Branch logic routes wrong

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.