Connect Telegram to Formbricks
When something happens in Telegram, Notis takes the next step in Formbricks. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Telegram to Formbricks
Turn Telegram feedback into a Formbricks contact
Capture a person's details from a Telegram message and add them as a Formbricks contact for organized follow-up.
Save structured Telegram answers as a survey response
Turn a Telegram message with survey answers into a Formbricks response for a survey you already run.
Create a Formbricks survey from a Telegram launch post
Use a Telegram channel announcement as the cue for Notis to create a survey that gathers feedback about a launch.
Record Telegram button feedback in Formbricks
When a user taps a Telegram inline button, save their selection as a Formbricks survey response.
Update a Formbricks response when feedback is corrected
Use an edited Telegram message to update an existing Formbricks response when a respondent corrects their answer.
Add new Telegram community members to Formbricks
Register new group members as Formbricks contacts so community onboarding and feedback can be organized.
Define a Formbricks attribute for recurring Telegram feedback
Use a Telegram message as the cue to define a reusable Formbricks attribute class for categorizing feedback.
Create a Formbricks webhook after a Telegram announcement
Use a Telegram channel post to cue creation of a Formbricks webhook for a feedback workflow endpoint.
Define a Formbricks action class from a Telegram workflow idea
Turn a clear Telegram workflow idea into a custom Formbricks action class for your environment.
Supported Triggers and Actions
Notis builds workflows that link Telegram to Formbricks. A trigger fires from one place; an action lands in another.
Telegram triggers
Formbricks actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Action Class
Tool to create a new action class. Use when defining custom action logic in your environment.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Attribute Class
Tool to create an attribute class in Formbricks. Use when you need to define new attribute classes for segmentation or attributes management.
New Message Received
Triggered when your bot receives a new message in a private chat, group, or supergroup. To receive every message in a group, Privacy Mode must be disabled for the bot in BotFather.
Create Contact
Tool to create a new contact. Use when you need to register a contact in a Formbricks environment.
New Channel Post
Triggered when a new post is published to a channel where your bot is an administrator.
Create Display
Tool to mark a survey as displayed or link it to a response. Use after obtaining the survey and environment IDs to register a display instance.
Callback Query Received
Triggered when a user taps an inline keyboard button attached to one of your bot's messages.
Create Survey Response
Tool to create a response for a survey. Use after collecting all survey answers.
Message Edited
Triggered when a message in a chat your bot can see is edited by its sender.
Create Survey
Tool to create a new survey. Use after defining survey details and questions.
New Chat Member
Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.
Create Webhook
Tool to create a new webhook. Use when you need to register an external endpoint to receive form response events.
Delete Attribute Class
Tool to delete an attribute class. Use when you need to remove an attribute class by its ID after confirming it's no longer needed.
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 recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
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.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
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.
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:
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.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Telegram and Formbricks
Connect any two apps with Notis in the middle.
Telegram and Formbricks, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Formbricks.