Carry a Notion feedback correction into Gist discussion
Keep a correction connected to the Gist comment it refers to.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Action
Update Gist Comment
Tool to update a Gist comment. Use when you need to modify an existing comment after confirming the gist_id and comment_id.
Why this helps
A correction recorded in Notion can leave a separate Gist conversation out of date.
- Carry a specific correction into the referenced Gist comment.
- Reduce duplicate follow-up across discussion threads.
- Keep the resolution close to the original conversation.
Setup
Build it in a few focused steps.
- 1Connect Notion and Gist to Notis once in the portal.
- 2Create an automation in the portal or tell Notis the intended outcome.
- 3Write one instruction asking Notis to update only the Gist comment identified by the new feedback, using its explicit revised text or status.
- 4Select New Comment as the trigger and choose a channel for run reports.
- 5Test with a feedback comment that includes the Gist ID, comment ID, and update text.
Questions about this workflow
What is required to update a comment?
The Gist ID, comment ID, and the intended replacement content should be clear in the Notion feedback.
Does this create a new Gist comment?
No. It updates an existing comment.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Gist. A trigger fires from one place; an action lands in another.
Notion triggers
Gist actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Gist Star
Tool to check if a gist is starred. Use when you need to determine if the authenticated user has starred a specific gist.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Gist Comment
Tool to delete a comment on a gist. Use when you have both the gist_id and comment_id and want to remove that comment. Example prompt: "Delete comment 42 from gist 'aa5a315d61ae9438b18d'".
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Gist
Tool to retrieve a specific gist by its ID. Use when you have a gist_id and need complete gist details.
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.
Get Gist Comment
Tool to get a specific comment on a gist. Use when you need to retrieve details of a particular comment given gist_id and comment_id.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Gist Revision
Tool to retrieve a specific gist revision. Use when you need details of a past state for an existing gist by commit SHA.
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.
List Gist Comments
Tool to list comments on a gist. Use after confirming the gist_id to retrieve comments for a specific gist. Example: 'List comments for gist abc123'.
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.
List Gist Commits
Tool to list the commit history of a gist. Use after you have the gist ID to review its revisions.
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.
List Gist Forks
Tool to list forks of a gist. Use after obtaining a gist_id to retrieve all forks for the gist.
Connect any two apps with Notis in the middle.
Notion and Gist, 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 Gist.