Refresh vision model research as your brief evolves
When the details change, refresh the model comparison without rebuilding the research process from scratch.
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
Get vision leaderboard
Access data from lmarena.ai.
Why this helps
A revised brief can leave old model research out of step with the actual task.
- Refresh vision model research after page content changes.
- Keep comparisons aligned with evolving requirements.
- Avoid manually retracing the same research steps.
Setup
Build it in a few focused steps.
- 1Connect Notion and LMArena to Notis once through the portal.
- 2Create an automation in the portal or ask Notis for a vision-model check when a brief changes.
- 3Write one plain-language instruction asking Notis to use the LMArena vision leaderboard in light of the changed brief.
- 4Select Notion Page Content Updated and choose where run reports should go.
- 5Test by updating the body of one real visual-analysis brief.
Questions about this workflow
Does it react to property edits too?
This trigger is for page body content. Choose a page-properties trigger if you need to respond to database property changes.
Can it interpret my project context?
Include what context Notis should consider in your prompt and the changed page content can guide the run.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to LMArena. A trigger fires from one place; an action lands in another.
Notion triggers
LMArena actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get code leaderboard
Access data from lmarena.ai.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get vision leaderboard
Access data from lmarena.ai.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get text leaderboard
Access data from lmarena.ai.
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 image-to-video leaderboard
Access data from lmarena.ai.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get text-to-video leaderboard
Access data from lmarena.ai.
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.
Search leaderboard models
Access data from lmarena.ai.
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 LMArena, 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 LMArena.