Reconnect updated research notes to active searches
As your research note evolves, get a fresh view of the searches you have saved in Melo.
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
List Searches
Tool to list all searches. use after authenticating to retrieve the user's searches.
Why this helps
After editing a brief, it is easy to forget which active searches could support the new direction.
- Resurface existing searches after meaningful note updates.
- Make it easier to restart work after a context switch.
- Connect evolving research to the searches already underway.
Setup
Build it in a few focused steps.
- 1Connect Notion and Melo to Notis once in the portal.
- 2Create the automation in the portal or ask Notis conversationally.
- 3Tell Notis to list your existing Melo searches when the selected research page content changes.
- 4Pick Page Content Updated for the relevant page or data source and choose a report channel.
- 5Test by editing an active research note and reviewing the returned list.
Questions about this workflow
Does this create a new Melo search from my edit?
No. It retrieves the searches you already have in Melo.
Can I target one page only?
Yes. Scope the Page Content Updated trigger to a specific page.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Melo. A trigger fires from one place; an action lands in another.
Notion triggers
Melo actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Cities
Tool to retrieve a list of cities with optional filters. use when you need to fetch available cities before processing location-specific data.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Searches
Tool to list all searches. use after authenticating to retrieve the user's searches.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Location Autocomplete
Tool to fetch location autocomplete suggestions. use when you have a partial location query and need possible matching locations from melo api. supports filtering by country and location type. use after forming the query string.
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.
Simulate Webhook
Tool to simulate sending a webhook event. use when testing webhook integrations. call after configuring endpoint and payload.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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 Melo, 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 Melo.