Connect Cloudflare to Telegram

When something happens in Cloudflare, Notis takes the next step in Telegram. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Send an answer to an inline button callback, shown as a chat notification or alert.

Build an automation Browse examples

Examples

Ways Notis can move work from Cloudflare to Telegram

Send Cloudflare DNS change alerts to Telegram

Review Cloudflare DNS records after a webhook starts the automation and send a concise Telegram alert about changes it can verify.

Get a scheduled Cloudflare firewall review

On a recurring schedule, review available Cloudflare firewall rules and send a Telegram digest of notable settings or gaps.

Check Cloudflare traffic with a Telegram poll

Run a scheduled Cloudflare analytics review and send a Telegram poll to help a team choose which traffic finding to investigate.

Send a Cloudflare security review as a file

Start a Cloudflare settings review by webhook and deliver a structured findings document to a Telegram chat.

Get a scheduled Cloudflare access settings check

Review available Cloudflare access settings on a recurring schedule and send a Telegram note about what the account data shows.

Forward a Cloudflare DNS review to a second chat

Review available Cloudflare DNS records when a webhook starts the automation, then forward a relevant existing Telegram message to another chat.

Check Telegram incident room membership

On a schedule, check the member count of a Telegram incident chat and alert when it differs from a baseline you provide.

Check Telegram chat details for a Cloudflare handoff

When a webhook starts a Cloudflare review, fetch current details for the Telegram destination chat to help verify the intended handoff location.

Supported Triggers and Actions

Notis builds workflows that link Cloudflare to Telegram. A trigger fires from one place; an action lands in another.

Cloudflare triggers

Telegram actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Answer Callback Query

Send an answer to an inline button callback, shown as a chat notification or alert.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Delete Message

Deletes a Telegram message, subject to time, message type, and chat permissions.

ActionInstant

Edit Message

Edits a Telegram message, subject to Telegram’s permissions and restrictions.

ActionInstant

Export Chat Invite Link

Generate a new primary chat invite link, revoking the previous one.

ActionInstant

Forward Message

Forwards a Telegram message; service messages and protected content cannot be forwarded.

ActionInstant

Get Chat Info

Retrieve current information about a chat.

ActionInstant

Get Chat Administrators

Lists chat administrators, excluding other bots.

ActionInstant

Get Chat History

Polls pending bot updates and filters the batch; this is not complete chat history.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a schedule (recurring or one-time), and a change in one of your Notis databases.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Scheduled triggers

Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.

Daily · 8:00Weekdays onlyOnce · Dec 13

Beta

Database triggers

Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.

Row addedProperty editedValue > limit

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.