Skip to content
Notis

Benchmark Your Prospects Against Their TikTok Ad Presence

When you create a new prospect database in Notion, Notis automatically starts collecting competitor TikTok Ads for market benchmarking.

Trigger

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.

Action

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.

Why this helps

New prospect databases are created but competitive TikTok ad benchmarking isn't part of your initial research setup.

  • Automatically start collecting competitor TikTok Ads when you create a prospect database
  • Benchmark prospect marketing strategies against their ad spend
  • Build competitive context into your prospect research from day one

Setup

Build it in a few focused steps.

  • 1Connect Notion and Adyntel integrations to Notis
  • 2Create an automation: 'When I create a new prospect database, start monitoring competitor TikTok Ads'
  • 3Choose where to send weekly summaries (Slack, email, or Telegram)
  • 4Test by creating a new prospect database and confirming ad collection begins
  • 5Notis will continuously gather TikTok ad data for benchmarking against your prospects

Questions about this workflow

How often does Notis collect TikTok ad updates?

Notis checks for new competitor TikTok Ads daily or weekly depending on your preferences. You can adjust collection frequency when setting up.

Can I apply this to an existing prospect database?

Yes - ask Notis to start monitoring an existing database and it will backfill recent competitor ad data.

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.

TriggerScheduled

Get Google Ads By Company

Retrieve all google ads for a given company domain.

ActionInstant

Webhook trigger

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

TriggerInstant

Search Meta Ads

Search the meta ad library.

ActionInstant

All Page Events

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

TriggerPolling

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.

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

New Comment

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

TriggerPolling

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

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 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.