Give important comments room for a decision
When a comment on a planning page raises a consequential question, Gamma can turn the thread and page context into a concise decision brief.
Trigger
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.
Action
Generate a Gamma
Create a new gamma generation. use to produce an ai-generated presentation/content. docs: https://developers.gamma.app/reference/generate-a-gamma
Why this helps
Important discussion in comments can be easy to miss when it is mixed with routine clarifications.
- Bring a decision request out of a busy comment thread.
- Give the discussion context without asking everyone to reread the whole page.
- Make assumptions and unresolved questions explicit.
Setup
Build it in a few focused steps.
- 1Connect Notion and Gamma to Notis once in the portal, and confirm Notion comment access is enabled.
- 2Ask Notis to create an automation that makes a Gamma decision brief when a new comment on planning pages raises a decision or blocker.
- 3Select Comment Created and scope it to the relevant page if appropriate.
- 4Choose where run reports should appear and test with one real decision comment.
Questions about this workflow
Does this work if Notion comments are not available to the connection?
Comment events require the Notion integration's Read comments capability. A connection authorized before that capability was enabled may need to be re-authorized.
Will every comment trigger a deck?
The selected trigger can detect new comments. Describe in the prompt which comments merit a brief and what context to include.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Gamma. A trigger fires from one place; an action lands in another.
Notion triggers
Gamma actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Generate a Gamma
Create a new gamma generation. use to produce an ai-generated presentation/content. docs: https://developers.gamma.app/reference/generate-a-gamma
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Gamma File URLs
Retrieve generation status and file urls. poll this endpoint every ~5 seconds until status is 'completed'. docs: https://developers.gamma.app/reference/get-gamma-file-urls
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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.
Connect any two apps with Notis in the middle.
Notion and Gamma, 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 Gamma.