Act on unwanted sender comments
Capture the sender in a Notion comment and let Notis add the matching address or domain to AgentMail's block list.
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
Add Allow/Block Rule
Add an email address or domain to an allow or block list for your mail.
Why this helps
Useful sender decisions buried in comments are easy to forget when inbox maintenance happens later.
- Turn a team decision into an inbox rule while it is fresh.
- Keep sender-handling decisions close to their discussion.
- Reduce repeat review of the same unwanted messages.
Setup
Build it in a few focused steps.
- 1Connect Notion and AgentMail to Notis once through the portal; enable Notion comment access if needed.
- 2Create an automation in the portal or ask Notis conversationally to block a sender identified in a Notion comment.
- 3Describe in one plain-language prompt how Notis should identify the address or domain and the decision to block it.
- 4Select the Notion Comment Created trigger and choose a run-report channel.
- 5Test with one real comment that clearly identifies a sender and confirm the rule.
Questions about this workflow
Does Notion comment access need to be enabled?
Yes. The Notion integration needs the Read comments capability, and an older connection may need reauthorization after enabling it.
Can the comment mention an address or a whole domain?
Yes. The instruction can ask Notis to apply the address or domain specified in the comment.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to AgentMail. A trigger fires from one place; an action lands in another.
Notion triggers
AgentMail actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Allow/Block Rule
Add an email address or domain to an allow or block list for your mail.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Your Email Inboxes
List the email inboxes you own (address, state).
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Update Email Message
Add or remove labels on a message; labels are the only mutable field.
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 Email Message
Permanently delete one message from an inbox you own; this is not reversible.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Update Email Inbox
Change an inbox's display name (the address itself is immutable).
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.
Remove Allow/Block Rule
Remove an email address or domain from an allow or block list.
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 AgentMail, 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 AgentMail.