Give a new planning view a snapshot of scheduled content
Create a new calendar or board view in Notion and have Notis check Dotsimple posts for content that may belong in the view's planning conversation.
Trigger
View Created
Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.
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
A new view can make existing work look like a blank slate when scheduled posts are not visible beside it.
- See existing scheduled work as a new planning lens is created.
- Avoid treating the queue as empty when it is not.
- Reduce manual cross-checking during setup.
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 conversationally.
- 3Write one instruction asking Notis to list relevant Dotsimple posts and summarize them when a social-planning view is created.
- 4Select View Created and choose a channel for run reports.
- 5Test with a real planning view.
Questions about this workflow
Will it add posts to the new view?
No. It retrieves the Dotsimple post list and reports relevant items.
Can it react only to calendar views?
Describe the desired view type in the instruction so Notis can use the event details when summarizing.
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.