Integrations
What ChurnNote connects to, and what it doesn't.
6 integrations work today. 3 are on the roadmap. Everything else on this page is something founders asked for and we have not committed to. That distinction is the whole point of the page.
Works with the tools already running your SaaS.
Every card below says exactly where it stands. Nothing is padded with a vague placeholder label to make the list look longer.
Available now
Billing
Stripe
AvailableConnect with a read-only restricted key. ChurnNote registers its own webhook and starts detecting churn immediately.
- Cancellations and scheduled cancellations
- Failed invoices and decline codes
- Subscription, plan and customer details
- Webhook registered automatically at connect time
How it works →
Lemon Squeezy
AvailableConnect with an API key and your store ID. ChurnNote registers a webhook with a per-store signing secret.
- Subscription cancellations and expiries
- Failed subscription payments and recoveries
- Customer, product and store details
- Webhook registered automatically at connect time
How it works →
Email sending
Custom SMTP
AvailableSend customer email from your own domain and mail server. Verified with a real test send before it goes live.
- Send from your own address, on your own domain
- Works with any SMTP provider (SSL, STARTTLS or none)
- Credentials encrypted at rest
- Falls back to ChurnNote delivery if your server rejects a send
How it works →
ChurnNote delivery
AvailableThe default. Nothing to configure: email goes out from a ChurnNote sending domain with your name on it.
- Used automatically when no custom SMTP is verified
- Replies routed back into your dashboard
- Bounces, complaints and unsubscribes suppressed automatically
- Currently powered by Resend
Account access
Google Sign-In
AvailableHow you sign in to ChurnNote. This is account access only, not a customer-data integration.
- Sign in and create your ChurnNote account
- No access to Gmail, Drive, Calendar or Contacts
- Reads nothing about your customers
Next on the roadmap
Customer Events API
PlannedOne endpoint to post product activity, so churn reasons can be matched to what a customer actually did before leaving. Built before per-vendor auth integrations, because it covers all of them.
- customer.created, customer.active, customer.inactive
- subscription.changed, feature.used, account.cancel_started
- Works with Clerk, Supabase Auth, Auth0 or your own auth
Paddle
PlannedThe next billing provider. Same merchant-of-record shape as Lemon Squeezy, so the cancellation and dunning model carries over.
- Subscription cancellations and pauses
- Failed and recovered payments
- Customer and plan details
Intercom
PlannedPull past support conversations alongside billing history, so a win-back knows what the customer already complained about.
- Prior conversations attached to the churned customer
- Support history as context for Reply Intelligence
- Richer, less generic win-back drafts
Requested by founders
Asked for, not committed. Votes decide what gets built after the roadmap above.
Two things people expect to see here
Google is sign-in, not a data source
Google is how you get into your ChurnNote account. ChurnNote does not read your Gmail, Drive, Calendar or Contacts, and learns nothing about your customers from it.
Anthropic and OpenAI are not listed as integrations
AI models categorise replies and draft emails inside ChurnNote. You do not connect an account, you cannot swap the provider, and you gain nothing by having one. Listing them here would imply a connection you make, which would be false. What leaves your account and what is retained is covered on the security page.
Request an integration
The roadmap above is ordered by what founders actually ask for. Tell us what you run on and what you would want ChurnNote to read from it.