Explore New Market Segments With Built-In Competitor Research
When you add a new market segment to Notion, Notis automatically searches and shows you competitor Google Ads in that space.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Get Google Ads By Company
Retrieve all google ads for a given company domain.
Why this helps
You explore new market segments in Notion but research competitor ads separately, leading to delayed or skipped market analysis.
- Automatic competitor ad research for every new market you explore
- See what competitors advertise in target segments before committing resources
- Make faster market entry decisions with real ad data in hand
Setup
Build it in a few focused steps.
- 1Connect your Notion workspace to Notis
- 2Create an automation: 'When I add a new market segment page, search competitor Google Ads in that market'
- 3Choose Slack, email, or another channel for results
- 4Test by adding a new market segment and checking for automatic ad results
- 5Going forward, every new segment you document triggers competitive ad research
Questions about this workflow
How specific can I be about market segments?
Very specific. Notis reads your segment name and description (e.g., 'Healthcare startups in Europe'). The more detail you provide, the more targeted the ad search.
Can I exclude certain competitors from these searches?
Yes - tell Notis which competitors or industries to focus on or skip when you set up the automation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Adyntel. A trigger fires from one place; an action lands in another.
Notion triggers
Adyntel actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Google Ads By Company
Retrieve all google ads for a given company domain.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Search Meta Ads
Search the meta ad library.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Search TikTok Ads
Tool to search for ads on tiktok using a keyword. use when you want to find ads related to a specific topic.
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.
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 Adyntel, 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 Adyntel.