Find code models for the task you just captured
Capture a coding need in Notion and get a timely view of leading code models without opening another research trail.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Get code leaderboard
Access data from lmarena.ai.
Why this helps
Choosing a model means pausing implementation to browse rankings and compare options.
- Check current code leaderboard data when a new database item arrives.
- Keep model research tied to the task that prompted it.
- Reduce the urge to open several comparison tabs.
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 tell Notis what code-model research you want when a Notion task is added.
- 3Write one plain-language instruction asking Notis to use the LMArena code leaderboard and summarize relevant choices.
- 4Select the Notion New Page trigger and choose where run reports should appear.
- 5Test with one real coding task page.
Questions about this workflow
Does this run for every new Notion page?
Choose the New Page trigger and describe in the prompt which coding needs matter. Notis interprets that instruction when it handles the event.
Will it install or select a model for me?
No. It retrieves leaderboard data and can summarize options; you decide what to use.
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.