Skip to content
Notis

See How Competitors Target Your Customer Segments on TikTok

When you add or update customer segments in Notion, Notis automatically searches TikTok Ads to show you competitor targeting for those segments.

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

You define customer segments but don't research how competitors actually target those same audiences on TikTok.

  • Understand competitor TikTok targeting for each of your customer segments
  • Avoid TikTok messaging that conflicts with competitor campaigns
  • See which segment targeting approaches competitors emphasize

Setup

Build it in a few focused steps.

  • 1Connect your Notion workspace to Notis
  • 2Tell Notis: 'When I add or update a customer segment, search TikTok Ads for that audience'
  • 3Choose Slack or email for results
  • 4Test by updating a segment property and checking for TikTok ad results
  • 5Notis will search competitor TikTok targeting every time you modify segments

Questions about this workflow

What kind of segment properties should I use?

Use properties like age range, industry, role, location, or interests. Notis searches TikTok Ads targeting those exact segments.

Can I search past segments I've already defined?

Yes - ask Notis to search TikTok targeting for your existing segments anytime you want.

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.