Review event-market signals at a set time
Bring the latest scored event signals into a planned review and avoid checking markets whenever a new alert catches your eye.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Pm Scorings
Latest direction+magnitude scorings for Polymarket events. Each row scores one (headline, market) pair with a direction (up/down/none), confidence (0-1), signed magnitude in points, composite tier (SKIP/WATCH/TRADE), and current market price.
Why this helps
Unstructured event-market checking can interrupt deep work and leave no clear review rhythm.
- Create a predictable time to review event signals.
- See direction, confidence, magnitude, tier, and market price together.
- Reduce ad hoc checking during focused work.
Setup
Build it in a few focused steps.
- 1Connect Notion and Gloria to Notis once through the portal.
- 2Create a scheduled automation in the portal and choose a cadence for event-market review.
- 3Write one instruction asking Gloria for the latest Polymarket event scorings and how Notis should report them.
- 4Choose a run-report channel and test with one scheduled run.
Questions about this workflow
What information is in each scoring?
Gloria returns the direction, confidence, signed magnitude, tier, and current market price for each headline-market pair.
Does this place bets?
No. It retrieves scoring information for your review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Gloria. A trigger fires from one place; an action lands in another.
Notion triggers
Gloria actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
News Ticker Summary
Get a 24-hour news summary for a specific token/ticker, combining internal news data with web search results. Returns decision-grade bullet points for fund managers and trading agents.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Pm Scorings
Latest direction+magnitude scorings for Polymarket events. Each row scores one (headline, market) pair with a direction (up/down/none), confidence (0-1), signed magnitude in points, composite tier (SKIP/WATCH/TRADE), and current market price.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
News
Get the latest news about a covered news topic, delivering the most recent 10 headlines.
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.
Recaps
Get a recap of the news or summary of a covered news topic over the past 12-24 hours.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
News By Keyword
Get the news about a topic by keyword, delivering the most recent 20 headlines.
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 Gloria, 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 Gloria.