Convert Form Submissions to Notion Tasks and Telegram Photo Alerts
Forms get submitted constantly. Turn them into Notion tasks and notify your team with a visual summary on Telegram so they can act.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Send Photo
Send photos to a telegram chat using the bot api.
Why this helps
Form submissions land in email or a third-party inbox, fragmenting the team's workflow. Neurodivergent members struggle to find responses and act on them.
- Centralize form responses in Notion instead of scattered across email
- Get instant Telegram alerts with visual summaries when submissions arrive
- Create a permanent, searchable record of all form data
- Enable fast triage and assignment of incoming submissions
Setup
Build it in a few focused steps.
- 1Connect Notion and Telegram to Notis.
- 2Create an automation: 'When a form submission webhook arrives, create a Notion task with the form data and send a Telegram photo alert showing a summary of the submission.'
- 3Select the trigger: 'Notis: Incoming Webhook'.
- 4Configure Telegram to send a photo or visual summary and choose your team channel.
- 5Test by submitting a form and confirming both the Notion task and Telegram photo appear.
Questions about this workflow
What does the Telegram photo show?
Your prompt controls it. For example: 'Generate a card showing the submitter name, email, and key details from the form' and Notis will format a visual summary.
Can I route different forms to different Notion databases?
Yes. Create separate automations and specify the destination: 'Form A submissions go to my Leads database, Form B submissions go to my Support database'.
What if the form has file attachments?
Notis can reference attachments: 'Include a link to any attached files in the Notion task' and add them to the Telegram alert as needed.
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.