Suspend a Google Workspace account when a Notion offboarding record is completed
Keep the final access step connected to the offboarding record. A clear status change can prompt Notis to suspend the matching account.
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
Suspend/Unsuspend Google Workspace User
Suspends or unsuspends a google workspace user account.
Why this helps
The final account suspension can be missed when offboarding steps live across separate tools.
- Keep the account action attached to the offboarding record.
- Reduce reliance on a person remembering a separate admin task.
- Make the completion condition explicit in one automation prompt.
Setup
Build it in a few focused steps.
- 1Connect Notion and Google Admin to Notis once through the portal.
- 2Create an automation and describe suspending the matching user only at the agreed offboarding status.
- 3Select the Notion Page Properties Updated trigger for the offboarding database.
- 4Choose a channel for run reports and test with one real completed offboarding record.
Questions about this workflow
Can the account be suspended before the record is complete?
Describe the exact status condition in the prompt and test it against the intended lifecycle before relying on the automation.
Can I reverse a suspension later?
Google Admin supports suspend and unsuspend through the listed action. Confirm your organization's process before using it.
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.