Explore text-to-video options when a concept takes shape
Capture the idea once, then get a focused view of text-to-video models while the concept is fresh.
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 text-to-video leaderboard
Access data from lmarena.ai.
Why this helps
Video ideas can be lost between capturing them and deciding how to explore them.
- Connect a newly captured concept with relevant video model research.
- Help turn a vague follow-up into one concise check.
- Keep the initial idea and ranking update together.
Setup
Build it in a few focused steps.
- 1Connect Notion and LMArena to Notis once through the portal.
- 2Create the automation in the portal or tell Notis to check text-to-video options for new video concepts.
- 3Write a single plain-language instruction describing which concepts matter and how the leaderboard findings should be reported.
- 4Select Notion Page Created and choose the report channel.
- 5Test with one real text-to-video concept page.
Questions about this workflow
Will the workflow check every newly created page?
The trigger can cover new pages broadly. Use the prompt to identify video concepts relevant to this check.
Does this generate a video?
No. It retrieves text-to-video leaderboard data and reports useful options.
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.