Make model choices easier to explain
Turn a documented model ID into useful context for the people starting the project.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Get Model
Tool to retrieve details of a specific model by its id. use after confirming the model id is valid.
Why this helps
An unfamiliar model identifier can make a project page harder to understand at a glance.
- Adds model details to a project kickoff discussion.
- Helps collaborators understand what the documented identifier refers to.
- Makes model selection context easier to review.
Setup
Build it in a few focused steps.
- 1Connect Notion and Anthropic administrator to Notis once in the portal.
- 2Create an automation in the portal, or ask Notis conversationally to explain a confirmed model ID when an AI project page is created.
- 3Use one plain-language instruction to retrieve the stated model details with Get Model and explain them without claiming they are a recommendation.
- 4Select the Notion Page Created trigger and scope it to the AI project data source.
- 5Test with one real project page containing a valid model ID and review the explanation.
Questions about this workflow
What if the model ID is invalid?
Get Model should be used after confirming the ID is valid. The instruction should ask Notis to report an unresolved ID clearly rather than guess.
Does this set the project model?
No. It retrieves details for a model and drafts an explanation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Anthropic administrator. A trigger fires from one place; an action lands in another.
Notion triggers
Anthropic administrator actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Message
Tool to create a new message completion. use when you need to generate assistant text given a conversation history.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Model
Tool to retrieve details of a specific model by its id. use after confirming the model id is valid.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List models
Tool to list available models. use when you need to see which models are available before selection.
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.
Prompt Caching
Tool to cache and reuse prompt content to reduce costs and latency. use after you have static prompt portions you intend to reuse across calls.
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 Anthropic administrator, 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 Anthropic administrator.