Skip to content
Notis

Keep competitor ad research moving from Notion

Update a watchlist entry with a competitor or campaign query, and let Apify look for relevant Facebook ads for your next review.

Trigger

Page Properties Updated

Triggers when properties of a Notion page are 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 property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.

Action

Search Facebook Ads

Scrape ads from the Meta/Facebook Ad Library by search query or page.

Why this helps

Remembering to revisit ad libraries competes with the work of building and running the business.

  • Starts a search after a watchlist update.
  • Makes current ad examples easier to review together.
  • Keeps the research request connected to its Notion context.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Apify to Notis once in the portal.
  • 2Create the automation in Notis by asking conversationally or through Automations in the portal.
  • 3Use one plain-language instruction to search the Facebook Ad Library based on each updated watchlist entry.
  • 4Pick the Notion Page Properties Updated trigger and set a channel for run reports.
  • 5Test by updating one watchlist entry with a real competitor or ad query.

Questions about this workflow

Can the search use a page name or query?

Yes. Include the competitor or search phrase in the watchlist item and describe that in the automation instruction.

Does it monitor every competitor continuously?

This workflow runs when the Notion watchlist page is updated. A recurring schedule would be needed for periodic searches.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Notion to Apify. A trigger fires from one place; an action lands in another.

Notion triggers

Apify actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Search Instagram

Search Instagram for places, profiles, and hashtags by keyword.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Get Snapchat Spotlight

Extract creator, caption, and engagement data from Snapchat Spotlight video URLs.

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

Get YouTube Transcript

Extract a full timestamped transcript plus video metadata from a YouTube video URL.

ActionInstant

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.

TriggerInstant

Search Facebook Ads

Scrape ads from the Meta/Facebook Ad Library by search query or page.

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

Search LinkedIn Profiles

Search LinkedIn profiles by keyword with job title, company, school, location, industry, seniority, and headcount filters.

ActionInstant

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.

TriggerInstant

List YouTube Comments

Extract complete comment threads from YouTube videos: text, authors, dates, votes, and replies.

ActionInstant

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.

TriggerInstant

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.

TriggerInstant

Connect any two apps with Notis in the middle.

Notion and Apify, 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 Apify.