Reply in the email thread when a Notion page gets a comment
When a comment lands on the Notion page tied to a client conversation, Notis replies inside the original Gmail thread, so the person on the other end sees the update where they already are instead of being asked to check Notion.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Action
Reply to email thread
Sends a reply within a specific gmail thread using the original thread's subject, requiring a valid `thread id` and correctly formatted email addresses. supports attachments via the `attachment` parameter with valid `s3key`, `mimetype`, and `name`.
Why this helps
Half the discussion happens in Notion comments and half in an email thread, and the client only ever sees one of them, so decisions get repeated or lost.
- The client sees the update in the thread they already know
- Notion and Gmail conversations stop drifting apart
- No copy-paste to keep one thread current with Notion
Setup
Build it in a few focused steps.
- 1Connect Notion and Gmail to Notis once from the portal.
- 2Create a new automation named Notion comment to thread reply.
- 3Write the prompt: when a new comment is added to this Notion page, reply in the related Gmail thread with the update.
- 4Choose the New Comment trigger, point it at the specific page, and pick a run-report channel.
- 5Add a test comment and confirm the reply appears in the correct thread.
Questions about this workflow
How does it know which thread to reply to?
You tell Notis which conversation the page relates to in the prompt, and it continues that thread rather than starting a new email.
Can I keep some comments internal?
Yes. Describe which comments should reach the client and Notis will skip the rest.
Does it reply instantly?
It runs when the comment event fires. You can also ask it to draft instead of send if you want a review step.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Gmail. A trigger fires from one place; an action lands in another.
Notion triggers
Gmail actions
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Modify email labels
Adds and/or removes specified gmail labels for a message; ensure `message id` and all `label ids` are valid (use 'listlabels' for custom label ids).
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.
Create email draft
Creates a gmail email draft, supporting to/cc/bcc, subject, plain/html body (ensure `is html=true` for html), attachments, and threading.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create label
Creates a new label with a unique name in the specified user's gmail account.
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.
Delete Draft
Permanently deletes a specific gmail draft using its id; ensure the draft exists and the user has necessary permissions for the given `user 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.
Delete message
Permanently deletes a specific email message by its id from a gmail mailbox; for `user id`, use 'me' for the authenticated user or an email address to which the authenticated user has delegated access.
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.
Fetch emails
Fetches a list of email messages from a gmail account, supporting filtering, pagination, and optional full content retrieval.
New Page
Triggers when a new page is added to a Notion database.
Fetch message by message ID
Fetches a specific email message by its id, provided the `message id` exists and is accessible to the authenticated `user id`.
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Fetch Message by Thread ID
Retrieves messages from a gmail thread using its `thread id`, where the thread must be accessible by the specified `user id`.
Connect any two apps with Notis in the middle.
Not just Notion and Gmail. Any combination from 1,000+ 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 Gmail.