New Subscriber
Requires a manual webhook Rule in Sendy. Repeated HTTP deliveries may produce duplicate runs: Sendy does not include an event ID. Resubscriptions are kept.
→
Ready-made Workflow
Notify Telegram about new Sendy subscribers
Connect your Sendy installation with its URL and API key. In the trigger Setup, copy the private webhook URL into a Sendy Rule for the matching event and list; keep that URL secret. Optionally restrict the trigger to one List ID. Only new events after activation are processed; existing subscribers are not imported. Sendy Rules do not provide an event ID: repeated HTTP deliveries or manual replays can produce duplicate outputs. Pausing stops FastHook processing; disable the manual Rule in Sendy separately when no longer needed. Select your Telegram bot and destination chat; the bot needs permission to post. Messages contain subscriber name, email and list name, so choose a private destination appropriate for subscriber data. No email is sent by this workflow. The sample contains fictional data.
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.
Notify Telegram of a new Sendy subscriber
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
Sendy
Connect your own Sendy account and review the provider settings used by this Workflow.
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 Sendy, 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.