Set up Canopus on your SaaS
Four things connect Canopus to your product: the onboarding that writes your strategy, read-only connectors for your numbers, a sending domain for your emails, and two endpoints your product calls. This is the full reference for each one.
OnboardingWhat the site scan reads, what the interview expects from you, and how the strategy becomes active.ConnectorsStripe and PostHog, read-only. Which key to create, which permissions it needs, what Canopus reads.Sending domainThe DNS records to publish, the verification window, the transactional subdomain and the reputation rules.CRM and leadsThe signed webhook your product calls, the public lead form endpoint, and how attribution travels with both.Email APISend your product emails (reports, alerts, receipts) through Canopus with one authenticated endpoint.MCP serverConnect Claude Code, Claude Desktop or claude.ai to Canopus, with one SaaS and the permissions you choose.
Who sets up what
Canopus is designed so that everything on its side is a few clicks, and everything on your side is a value to paste or a small snippet to drop in your codebase.
In the Canopus app
- Run the onboarding: site scan, brief, interview, strategy.
- Connect Stripe and PostHog with read-only keys.
- Add the sending domain and copy the records Canopus shows you.
- Generate the webhook secret, the lead form key and the API key on their settings screens.
In your product and your DNS
- Publish the DNS records for your sending domain (your registrar, once).
- Call the CRM webhook from your backend when a user signs up, pays, fails to pay or churns.
- Point a form on your site at the lead endpoint, or post to it from your own JavaScript.
- Pass the cnp parameter and the UTM values your landing page receives back into those two calls.
- If you use the email API: store the key and call one endpoint.