Find out whether a content request is already in the post queue
A request in a Notion comment can be easy to lose. Have Notis check Dotsimple posts and report whether related content is already planned.
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
List Posts
Tool to list all posts in the workspace with optional pagination. use when you need to fetch paginated posts after obtaining a valid auth token.
Why this helps
Requests scattered through comments create repeated checking and uncertainty about whether someone has already acted.
- Check for existing scheduled content before adding another task.
- Reduce duplicate follow-up across comments and the social queue.
- Receive the result where you prefer Notis run reports.
Setup
Build it in a few focused steps.
- 1Connect Notion and Dotsimple to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it in plain language.
- 3Tell Notis in one instruction to inspect relevant Dotsimple posts for each new content-request comment and report likely matches.
- 4Select Comment Created, set a page filter if useful, and choose a report channel.
- 5Test with a real request comment.
Questions about this workflow
Does it understand every comment as a request?
Describe what counts as a content request in the automation instruction; review the result before acting on it.
Is comment access required?
Yes. The Notion connection needs the Read comments capability, and may need re-authorization after that capability is enabled.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Dotsimple. A trigger fires from one place; an action lands in another.
Notion triggers
Dotsimple actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Tag
Tool to create a new tag in dotsimple. use when you need to categorize content with custom tags. example: create a tag named "news" with color "#38bdf8".
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Media Files
Tool to delete multiple media files in the workspace. use after confirming unwanted files. call this when you have a list of media ids to remove. returns success status.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Tag
Tool to delete a tag by its uuid. use when you need to remove a specific tag; ensure the uuid is correct before invoking.
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 Media File
Tool to retrieve details of a specific media file. use when you have the mediafileid and need its metadata.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Tag by UUID
Tool to retrieve details for a specific tag by uuid. use when you need full tag information after obtaining its identifier.
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 Accounts
Tool to list all connected social media accounts in the workspace. use when you need to retrieve available accounts before posting or scheduling content.
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 Autoresponders
Tool to list all autoresponders. use when you need to browse through your autoresponder setup.
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 Media Files
Tool to list all media files with optional pagination. use when you need to retrieve or browse uploaded media files page by page.
Connect any two apps with Notis in the middle.
Notion and Dotsimple, 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 Dotsimple.