Follow Polar sales and renewals in Telegram.
Connect Polar webhooks to PushTheSales and get new purchases, renewals and refunds as updates you can read from your phone.
Connect Polar notifications Read the setup steps ↓Does this sound familiar?
- You check Polar after every launch or campaign.
- A settled refund can pass unnoticed between other account activity.
- Readable product names are buried behind Polar identifiers.
Polar events become clear Telegram messages, grouped under the right app.
How to make it work.
Copy your private webhook link.
Open PushTheSales Settings and copy your workspace ingestion URL. The token is a credential, so keep it out of public repositories and browser code.
Create a Polar webhook endpoint.
Select the correct organization, open its Webhooks settings and add an endpoint. Choose Raw JSON, name it PushTheSales and paste the private ingestion URL.
Choose order and subscription events.
Select order.created; subscription.created, subscription.active, subscription.updated, subscription.canceled, subscription.uncanceled and subscription.revoked; and order.refunded. order.created is the economic event used by PushTheSales.
Link Telegram and organize products.
Confirm your Telegram account in Settings, enable the event categories you want and assign Polar products to apps in Manage products. Product and price labels make messages readable.
Test with an isolated sandbox path.
For a Polar sandbox organization or CLI test, append ?mode=test to the test endpoint URL so its events do not affect production metrics. Use the production URL without that parameter and verify both paths.
Keep payments and lifecycle changes clear.
Purchases and recurring cycles.
Supported Polar billing reasons let the event appear as an initial purchase or a subscription cycle. The notification includes the amount and original currency when the event is monetary.
Completed refunds.
Use order.refunded for applied refunds. refund.created can describe a pending refund, so it is not relied on for the settled-refund notification.
Apps within one organization.
Assign each Polar product to its project and add labels. The organization can stay shared while the dashboard still separates each app’s results.
Questions about this setup.
Should I select order.paid as well?
Use order.created for this integration. Polar may emit order.paid around the same purchase, but the current flow deliberately uses order.created as the economic event.
Will pending refunds be announced as refunds?
The configured flow uses order.refunded, which represents an applied refund. refund.created is ignored for this purpose.
Can I test Polar safely?
Yes. Use a separate sandbox endpoint with ?mode=test on its PushTheSales URL and verify the event and notification before enabling live deliveries.
Can Polar and Stripe products share an app?
Yes. Assign products from both providers to that app. Each app can use one provider root per payment source.
Polar events become clear Telegram messages, grouped under the right app.
Start in PushTheSales, then follow the setup for your provider.
Connect Polar notifications