Keep vendor decisions grounded in G2 overviews

Update a vendor record in Notion and ask Notis to retrieve its G2 overview for a quick decision refresher.

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

Get product overview

Search G2.com to discover software products, compare pricing and categories, and read customer reviews all in one place. Get detailed product overviews and ratings to make informed decisions about business software.

Why this helps

A vendor decision can become hard to revisit when the original comparison context is scattered or stale.

Bring ratings and product details back into view after a record changes.
Make it easier to explain why a vendor remains under consideration.
Spend less time reconstructing the decision from old notes.

Setup

Build it in a few focused steps.

1Connect Notion and G2 to Notis once in the portal.
2Create a portal automation or describe the automation to Notis conversationally.
3Ask Notis in one instruction to retrieve a G2 overview when a vendor record changes and summarize decision-relevant details.
4Select the Notion Page Properties Updated trigger for the vendor database and choose a reporting channel.
5Test by updating one real vendor record and reviewing the overview.

Questions about this workflow

Will this replace information in my vendor record?

The automation retrieves G2 information for review. Its instruction can ask Notis to report the findings without changing the record.

What can a G2 overview help me revisit?

It can provide product details and ratings that support a fresh look at a vendor.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Supported Triggers and Actions

Notis builds workflows that link Notion to G2. A trigger fires from one place; an action lands in another.

Notion triggers

G2 actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Get product reviews

ActionInstant

Webhook trigger

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

TriggerInstant

List categories

ActionInstant

All Page Events

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

TriggerPolling

Search software

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

List category products

ActionInstant

New Comment

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

TriggerPolling

Get product overview

ActionInstant

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

Get product pricing

ActionInstant

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

Add Notis to G2 Pricing