Keep new views understandable to the whole team
When someone creates a new view, check any explicitly flagged term so the view's purpose is easier to grasp.
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
Get Word Definition V2
Tool to retrieve definitions, phonetics, origin, and meanings of a given word using freedictionaryapi v2. use when you need comprehensive lexical data for a specific word.
Why this helps
A view name that makes sense to its creator may leave everyone else guessing what it shows.
- Clarify a view label as it is introduced.
- Help teammates understand new ways to organize the same work.
- Avoid searching for terminology while trying to find the right view.
Setup
Build it in a few focused steps.
- 1Connect Notion and Dictionary api to Notis once in the portal.
- 2Create an automation in the portal or ask Notis in a connected channel.
- 3In plain language, ask Notis to look up a word in the new view's name or context only when explicitly flagged for clarification.
- 4Choose View Created and a channel for run reports.
- 5Test by creating a view with one flagged unfamiliar term in its name or context.
Questions about this workflow
Which view details are available with this trigger?
The event includes the view type and its parent, so the prompt should use the context available from the new view event.
Can it define every new view name?
It can be instructed to do so, but checking only explicitly flagged unfamiliar words can keep the workflow focused.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Dictionary api. A trigger fires from one place; an action lands in another.
Notion triggers
Dictionary api actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Word Definition V2
Tool to retrieve definitions, phonetics, origin, and meanings of a given word using freedictionaryapi v2. use when you need comprehensive lexical data for a specific word.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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 Dictionary api, 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 Dictionary api.