C
→Telegram Bot logo

Ready-made Workflow

Notify Telegram when a Cal.com booking is cancelled

Connect Cal.com using a dedicated API key. FastHook creates a signed account-level webhook when activated and removes owned subscriptions after the last consumer is paused. Team-owned booking links may need their own team/event-type hook. Cal.com sends booking data to the selected destination. No account IDs, resource IDs or secrets are included. Manual reruns can duplicate destination effects. Test with fictional bookings before activation. Choose your Telegram bot and chat before activation. Messages contain the title, booking UID, start time and event time; no email addresses are copied.

Use this templateCreates a new Draft · no credentials copied

What gets copied

The working graph, not another user's secrets

FastHook recreates every Step, route, field mapping, and setting with new IDs in your workspace.

Step 1 · Calcom · Trigger

Booking cancelled

Signed Cal.com BOOKING_CANCELLED webhook. Account-level events; access and event generation depend on Cal.com plan and role.

Step 2 · Telegram Bot

Notify Telegram when a Cal.com booking is cancelled

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 accounts in the Draft

1

Calcom

Connect your own Calcom account and review the provider settings used by this Workflow.

2

Telegram Bot

Connect your own Telegram Bot account and review the provider settings used by this Workflow.

Explore connected apps

Questions

Template FAQ

Does the template copy someone else's credentials?

No. FastHook creates a disconnected Draft. Connect your own Calcom, Telegram Bot accounts before activation.

Can I change the Steps and mappings?

Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.

What is copied into my workspace?

FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.

When does the Workflow start running?

Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.