Any Subscription Event
Start the Workflow when any subscription event occurs.
Ready-made Workflow
Send a Telegram notification when RevenueCat reports a subscription event, such as a purchase, renewal or cancellation. Each message includes the event type and event ID. Connect RevenueCat through OAuth using the API v2 Project ID from Project settings, then select your Telegram bot and destination chat. The bot must be allowed to post there. Any Subscription Event also accepts official TEST notifications, which let you check delivery without a purchase. Replace the fictional example with a real test event before testing delivery. Repeated provider events are deduplicated; a manual workflow replay can send another message. Pausing stops processing immediately; the FastHook-owned webhook is removed by scheduled cleanup.
What gets copied
FastHook recreates every Step, route, field mapping, and setting with new IDs in your workspace.
Start the Workflow when any subscription event occurs.
Telegram Bot API sendMessage. Use this method to send text messages. On success, the sent [Message](/bots/api/types/message.md) is returned.
Before activation
Connect your own RevenueCat account and review the provider settings used by this Workflow.
Connect your own Telegram Bot account and review the provider settings used by this Workflow.
Questions
No. FastHook creates a disconnected Draft. Connect your own RevenueCat, Telegram Bot accounts before activation.
Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.
FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.
Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.