Route Customer Feedback Into a Telegram Poll for Team Input
Customer feedback is gold. Route it to a Telegram poll and ask your team how to respond.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Send Poll
Send a native poll to a telegram chat using the bot api.
Why this helps
Customer feedback arrives through multiple channels and gets lost or goes unaddressed. Neurodivergent teams struggle to coordinate response.
- Get quick team input on customer feedback without long meetings
- Route feedback through a single, visible channel
- Build a record of feedback and team response
- Enable fast customer response with team alignment
Setup
Build it in a few focused steps.
- 1Connect your feedback tool and Telegram to Notis.
- 2Create an automation: 'When customer feedback arrives via webhook, send a Telegram poll asking the team: What should our response be? Options: Implement it, Consider it, Decline it, Ask for more info.'
- 3Select the trigger: 'Notis: Incoming Webhook from [feedback tool]'.
- 4Configure Telegram as your action and choose your team channel.
- 5Test by submitting feedback and verify the Telegram poll appears.
Questions about this workflow
Can I customize the poll options based on feedback type?
Yes. Add logic to your prompt: 'For feature requests, ask Implement/Decline/Backlog. For bugs, ask Priority High/Medium/Low.' and Notis will adjust.
What happens to the poll results?
The poll results are visible in Telegram and can be logged. You can also create a follow-up automation to record the result back to Notion.
Can I tag specific team members in the poll?
Yes. Request it in your prompt: 'Tag @product and @engineering so they see it immediately' and Notis will include those mentions.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Telegram. A trigger fires from one place; an action lands in another.
Notion triggers
Telegram actions
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Answer Callback Query
Use this method to send answers to callback queries sent from inline keyboards. the answer will be displayed to the user as a notification at the top of the chat screen or as an alert.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Delete Message
Delete a message, including service messages, with certain limitations.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Edit Message
Edit text messages sent by the bot.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Export Chat Invite Link
Generate a new primary invite link for a chat; any previously generated primary link is revoked. the bot must be an administrator in the chat for this to work and must have the appropriate administrator rights.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Forward Message
Forward messages of any kind. service messages can't be forwarded.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Get Chat Info
Get up to date information about the chat (current name of the user for one-on-one conversations, current username of a user, group or channel, etc.).
New Page
Triggers when a new page is added to a Notion database.
Get Chat Administrators
Get a list of administrators in a chat. on success, returns an array of chatmember objects that contains information about all chat administrators except other bots.
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Get Chat History
Get chat history messages. note: this uses the getupdates method with specific parameters to retrieve historical messages.
Connect any two apps with Notis in the middle.
Not just Notion and Telegram. Any combination from 985+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Telegram.