Notice client concerns in your working notes
A sentiment check can bring a concern to your attention while there is still time to respond thoughtfully.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Classify Text
Tool to classify text. Use when you need to obtain labels and confidence scores from a trained MetatextAI model for given text.
Why this helps
Concerns can be easy to miss in a stream of client notes, especially when delivery work is busy.
- Highlights potentially negative or uncertain language for review.
- Helps prioritize client follow-up.
- Adds a repeatable check to updated notes.
Setup
Build it in a few focused steps.
- 1Connect Notion and MetatextAI to Notis once through the portal.
- 2Create an automation and describe how client-note sentiment should be classified.
- 3Ask for a sentiment label with brief evidence, and have uncertain results clearly marked for human review.
- 4Choose Page Content Updated for the relevant client notes and select a run-report channel.
- 5Test on one updated note and confirm the classification is useful before relying on it.
Questions about this workflow
Does a negative label prove a client is unhappy?
No. Treat the label as a review signal and consider the page context before taking action.
Can it cover only a particular notes database?
The Page Content Updated trigger can be scoped to a data source.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Metatextai. A trigger fires from one place; an action lands in another.
Notion triggers
Metatextai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Chat Completions
Tool to generate chat completions. Use when you need OpenAI-compatible conversational responses.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Classify Text
Tool to classify text. Use when you need to obtain labels and confidence scores from a trained MetatextAI model for given text.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Policy Guardrails
Tool to create a policy guardrail. Use when you need to define automated guardrails for content in a specific application.
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 Guardrail Policy
Tool to delete a guardrail policy. Use when you need to remove a policy by ID for a specific application after confirming valid application and policy IDs.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Evaluate Messages
Tool to evaluate LLM messages against policies/guardrails. Use after generating model output to get violation details or corrections.
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.
Run Extraction
Tool to run information extraction. Use when you need to extract structured data from text.
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.
Generate Text
Tool to generate text for a project model. Use when you need LLM completions or chat responses. Supports both prompt and message-based inputs with temperature, stop-sequence, and token limits.
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 Applications
Tool to retrieve a list of all existing applications. Use when you need to view application IDs, names, and descriptions.
Connect any two apps with Notis in the middle.
Notion and Metatextai, 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 Metatextai.