Get Creem sales updates in Telegram.
Connect your Creem store to PushTheSales and follow completed checkouts, recurring payments and subscription changes through Telegram.
Connect Creem notifications Read the setup steps ↓Does this sound familiar?
- Your store activity is hidden inside another dashboard.
- Test and live events become difficult to tell apart.
- Raw event names do not show which app generated the update.
Creem store activity reaches Telegram with readable app and product labels.
How to make it work.
Create the production endpoint.
In the Creem dashboard for the store, open Developers → Webhooks and create an endpoint. Paste the private PushTheSales ingestion URL.
Select the checkout and subscription events.
Include checkout.completed; subscription.paid, subscription.active, subscription.trialing, subscription.past_due and subscription.update; subscription.scheduled_cancel, subscription.canceled and subscription.paused; refund.created and dispute.created.
Keep Test Mode separate.
Creem Test Mode has its own API keys, webhooks and signing secrets. Create a separate test endpoint with ?mode=test on its PushTheSales URL. Use the production URL without that parameter for live events.
Link Telegram and choose categories.
Connect Telegram in Settings and choose the sales, renewals, churn and refunds you want to receive. Override the global preferences when an app produces too much noise.
Verify the route to live.
Complete a test checkout and confirm ingestion and product discovery. Before live traffic, make sure the HTTPS route is reachable and that Cloudflare bot protections or a WAF are not challenging Creem deliveries.
Follow the store from checkout through cancellation.
Readable app and product names.
Assign Creem products to the right app and use labels such as Pro Monthly. The dashboard can then filter one project without losing the store-wide picture.
State changes are not always payments.
A subscription update or scheduled cancellation changes lifecycle state. It does not automatically represent a new sale. The supported event and category determine the notification.
Webhook-friendly network configuration.
Creem does not publish static webhook source IPs for this flow. Use the secret ingestion URL over HTTPS and avoid IP allowlists that would block valid deliveries.
Questions about this setup.
Can live and test checkouts share one endpoint?
Keep them separate. Add ?mode=test to the Test Mode PushTheSales URL so test data stays isolated from production metrics.
Which event represents a completed checkout?
checkout.completed covers the completed checkout flow. Subscription events keep recurring lifecycle state current.
Does scheduled cancellation mean immediate churn?
No. It records an upcoming cancellation. The effective cancellation and expiration state determine when churn appears.
Can I keep my own Creem webhook?
Creem can deliver to multiple compatible endpoints. Add PushTheSales as another destination, or use forwarding when your flow needs a single intermediary.
Creem store activity reaches Telegram with readable app and product labels.
Start in PushTheSales, then follow the setup for your provider.
Connect Creem notifications