| name | sales-sendowl |
| description | SendOwl platform help — sell and securely deliver digital products (ebooks, software, audio, video, courses) with download-link protection, PDF stamping, license keys, drip, subscriptions, and upsells, plus a REST API (Basic Auth) and HMAC-signed webhooks. Use when SendOwl download links are being shared and you need expiring/limited links, verifying the X-SENDOWL-HMAC-SHA256 webhook signature, syncing SendOwl orders to a CRM or spreadsheet via the API, issuing or checking software license keys, setting up subscriptions or drip content, the order_completed webhook isn't firing, or weighing SendOwl's plan tiers and recent price changes against Gumroad/Payhip/Lemon Squeezy. Do NOT use for choosing between digital-product platforms in general (use /sales-digital-products) or checkout-conversion strategy across carts (use /sales-checkout). |
| argument-hint | [describe what you need help with in SendOwl] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","digital-products","platform"] |
| github | https://github.com/SendOwl |
SendOwl Platform Help
SendOwl sells and securely delivers digital products — download links with expiry/limits, PDF stamping, license keys, drip content, subscriptions, bundles, and upsells — with a REST API and HMAC-signed webhooks.
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
Ask only what you can't infer from the user's message:
-
What are you trying to do?
- A) Stop customers from sharing download links / tighten delivery security
- B) Build an API or webhook integration (sync orders to a CRM, warehouse, Slack, or your own app)
- C) Set up products, subscriptions, drip, license keys, or upsells
- D) Compare SendOwl plans/pricing to alternatives, or weigh a price change
- E) Troubleshoot a broken flow (webhook not firing, email not sending, file not delivering)
-
Are you connecting SendOwl to another tool? Which one, and which direction should data flow?
Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
Step 2 — Route or answer directly
Map the request to the right home. When routing, give the exact command.
| The user's need | Route to |
|---|
| "Which platform should I sell on — SendOwl, Gumroad, Payhip?" | /sales-digital-products {question} |
| Checkout-conversion strategy (order bumps, upsells, cart abandonment) across carts | /sales-checkout {question} |
| VAT/GST/sales-tax handling for global sales (SendOwl is not a merchant of record) | /sales-merchant-of-record {question} |
| Pricing/packaging strategy for the product itself | /sales-digital-products {question} |
| Recurring-access / course-membership strategy | /sales-membership {question} |
| Wiring SendOwl events into other tools via an iPaaS | /sales-integration {question} |
If it's a SendOwl setup, API, webhook, delivery-security, or pricing question, answer it here using Step 3.
Step 3 — SendOwl platform reference
Read references/platform-guide.md for the full platform reference — capabilities and automation surface, pricing/plan gates, data model, integration recipes (order→CRM sync, webhook listener, license issuing), and code examples.
