Check existing Google groups when a Notion database is created
Starting a new operational database can be a good moment to check the groups that support its process. Notis can bring that inventory into the setup step.
Trigger
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.
Action
List Google Workspace Groups
Lists google workspace groups with optional filtering and pagination.
Why this helps
New processes can be documented without checking whether their team group already exists.
- Add a group inventory check to a new process setup.
- Reduce avoidable duplicate group requests.
- Make existing admin structure easier to consider early.
Setup
Build it in a few focused steps.
- 1Connect Notion and Google Admin to Notis once through the portal.
- 2Create an automation and describe listing groups when a relevant process database is created.
- 3Select the Notion Database Created trigger and use the prompt to identify relevant databases.
- 4Choose a channel for run reports and test with one real database creation.
Questions about this workflow
Does creating any Notion database trigger this event?
The event is workspace-wide. Describe the relevant process databases in the prompt and test the behavior.
Does the automation create a group?
No. This workflow lists existing Google groups for a setup review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Google Admin. A trigger fires from one place; an action lands in another.
Notion triggers
Google Admin actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Alias to Google Workspace User
Adds an email alias to a google workspace user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add User to Google Workspace Group
Adds a user to a google workspace group with the specified role.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Google Workspace Group
Creates a new google workspace group with the specified details.
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.
Create Google Workspace User
Creates a new google workspace user with the specified details.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Google Workspace User
Deletes a google workspace user permanently. this action cannot be undone.
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.
Get Google Workspace Group Details
Retrieves detailed information about a google workspace group.
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.
Get Google Workspace User Details
Retrieves detailed information about a google workspace user.
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.
List Google Workspace Group Members
Lists all members of a google workspace group with optional filtering and pagination.
Connect any two apps with Notis in the middle.
Notion and Google Admin, 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 Admin.