Refresh competitor ad research when your tracker evolves
When you update the structure of a competitor tracker, let Apify gather relevant ad examples for the research it is meant to support.
Trigger
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.
Action
Search Facebook Ads
Scrape ads from the Meta/Facebook Ad Library by search query or page.
Why this helps
A more useful tracker can still sit empty when collecting fresh examples is another manual task.
- Uses tracker schema updates to cue a related research pass.
- Helps populate evolving competitor research with ad examples.
- Keeps the search topic tied to the tracker purpose.
Setup
Build it in a few focused steps.
- 1Connect Notion and Apify to Notis once in the portal.
- 2Create an automation conversationally or through Automations in the portal.
- 3Provide one plain-language instruction to search the Ad Library when the competitor tracker schema changes in a relevant way.
- 4Select the Notion Data Source Schema Updated trigger and a channel for run reports.
- 5Test after a planned schema update that makes the tracker more useful for ad research.
Questions about this workflow
Can it react only to certain schema changes?
The event includes details about changed properties. Describe which kinds of change should prompt a search in the automation instruction.
Will it fill every tracker row?
The Apify action searches the Ad Library and reports results. Review the examples and decide what belongs in the tracker.
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.
Search Instagram
Search Instagram for places, profiles, and hashtags by keyword.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Snapchat Spotlight
Extract creator, caption, and engagement data from Snapchat Spotlight video URLs.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get YouTube Transcript
Extract a full timestamped transcript plus video metadata from a YouTube video URL.
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.
Search Facebook Ads
Scrape ads from the Meta/Facebook Ad Library by search query or page.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Search LinkedIn Profiles
Search LinkedIn profiles by keyword with job title, company, school, location, industry, seniority, and headcount filters.
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.
List YouTube Comments
Extract complete comment threads from YouTube videos: text, authors, dates, votes, and replies.
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 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.