Integrations

CoEditor CRM is built to sit alongside the systems you already use for payments and access control—not replace them wholesale.

Stripe

Stripe remains the billing source of truth: products, prices, subscriptions, invoices, and payment outcomes.

Connect Stripe in publication Settings, then enable webhooks so new and updated billing objects flow into Customers and Subscriptions without manual CSV work.

Typical outcomes when webhooks are healthy:

• New checkout or subscription flows create or update CRM customer records
• Subscription status changes in Stripe reflect on CRM subscription views
• Product and price changes stay aligned for reporting and operations

Piano

Piano is commonly used for user accounts, access, registrations, and entitlement-style behaviour.

Because Piano often allows only one webhook URL, CoEditor provides a Piano proxy you paste into Piano once; CRM and optional legacy endpoints can still receive the same event stream.

Configure Piano credentials and the proxy in Settings, then complete the Piano base webhook generation on the same screen.

Digital products and ebooks

Many publishers sell digital editions or ebooks through Piano, Stripe, or both. CoEditor can track those offers in the platform when:

• The provider connection (Stripe and/or Piano) is complete in Settings
• Webhooks are active so creates and updates propagate
• Your publication’s product catalogue is wired to the SKUs or Piano resources you expect in CRM

If a title appears in the provider admin UI but not in CoEditor, treat it like a sync issue: confirm webhooks first, then use the Webhooks FAQ or contact support with the product id and provider name.

Where to configure everything

Related documentation

• Webhooks overview
• Set up webhooks
• Webhooks FAQ
• Data exports
• Data Export v2 Architecture
• App API Routes — cancellation and winback on your sites