SendGrid logo
→Telegram Bot logo

Ready-made Workflow

Notify Telegram when SendGrid delivers an email

Connect SendGrid with an API key that can read your username and create, read, update and delete Event Webhooks. FastHook creates a signed webhook for Email Delivered. Connect Telegram and choose a chat where the bot can post. The notification includes recipient email, message ID and event ID, so choose a private destination when appropriate. Delivered means accepted by the recipient mail server, not inbox placement or reading. The fictional example checks mappings only. Real acceptance requires an eligible SendGrid Email API plan, a verified sender and one approved test email. Provider retries are deduplicated; manually replaying a workflow can send another notification.

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 · SendGrid · Trigger

Email Delivered

An email was accepted by the recipient mail server. This does not prove inbox placement or reading.

Step 2 · Telegram Bot

Notify Telegram of email delivery

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

SendGrid

Connect your own SendGrid 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 SendGrid, 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.