Address Customer Pain Points Knowing Competitor Solutions
When you document customer feedback in Notion, Notis automatically searches Meta Ads to show how competitors position solutions for the same pain points.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Search Meta Ads
Search the meta ad library.
Why this helps
You identify customer problems but don't research how competitors are solving them in their Meta Ads.
- See competitor solutions to customer pain points in their Meta Ads automatically
- Position your solution against competitor offerings before building
- Avoid customer solution conflicts with competitor positioning
Setup
Build it in a few focused steps.
- 1Connect Notion and Adyntel to Notis
- 2Create an automation: 'When I document customer feedback or pain points, search Meta Ads for similar problem solutions'
- 3Select Slack or email for results
- 4Test by adding customer feedback to Notion and checking for competitor solution ads
- 5Notis will search competitor Meta Ads for every pain point you document
Questions about this workflow
How does Notis identify which pain points to search for?
Notis reads your customer feedback to extract key problems mentioned (e.g., 'manual data entry is slow'). It searches Meta Ads for solutions to those problems.
Can I search Meta Ads for pain points I've already documented?
Yes - ask Notis anytime to search competitor Meta Ads for solutions to any existing customer feedback.
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.