Give a documented audience playbook a matching list
When your audience playbook adds a new segment, let Notis set up its corresponding customer list from the description.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Create customer list
Createcustomerlist tool will create a customer list in google ads.
Why this helps
A new audience defined in a playbook can be overlooked when the next step is a separate account setup task.
- Connect playbook updates to audience setup.
- Keep the audience description and list creation instruction together.
- Reduce the chance of a documented segment staying only in notes.
Setup
Build it in a few focused steps.
- 1Connect Notion and Google Ads to Notis once in the portal.
- 2Create an automation that creates a customer list when the specified audience playbook documents a new segment.
- 3Select the Notion Page Content Updated trigger for that playbook and choose a channel for run reports.
- 4Test with one real segment update and check the created list.
Questions about this workflow
Will every content update create a list?
Describe in the prompt that Notis should act when a new segment is documented, and scope the trigger to the playbook page.
Does it add audience members too?
No. It creates the customer list container.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Google Ads. A trigger fires from one place; an action lands in another.
Notion triggers
Google Ads actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create customer list
Createcustomerlist tool will create a customer list in google ads.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Campaign By Id
Getcampaignbyid tool will return details of a campaign in google ads.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get campaign by name
Getcampaignbyname tool will run a sql getcampaignbyname in google ads.
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.
Get customer lists
Getcustomerlists tool will list all customer lists in google ads.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Add or remove to customer list
Addorremovetocustomerlist tool will add a contact to a customer list in google ads. note: it takes 6 to 12 hours for changes to be reflected in the customer list.
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 Google Ads, 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 Google Ads.