Skip to content
Notis

Understand how visitors respond to a new offer

Add an offer to Notion and have Notis review Livesession sessions for signs of confusion, drop-off, or strong buying intent.

Trigger

New Page

Triggers when a new page is added to a Notion database.

Action

List Live Sessions

Tool to list live sessions. use when you need paginated session data filtered by criteria after authentication.

Why this helps

Launching an offer can create a rush of manual session review just when attention is needed elsewhere.

  • Spot questions or hesitation around a newly launched offer.
  • Get a concise review without opening sessions one by one.
  • Use observed visitor behavior to prioritize follow-up improvements.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Livesession to Notis once through the portal.
  • 2In Automations, create an automation and describe how to review recent Livesession sessions when a new offer page is added in Notion.
  • 3Choose the Notion New Page trigger and select a channel for run reports.
  • 4Test by adding one real offer page and reviewing the resulting session summary.

Questions about this workflow

Does this create or edit the offer page?

No. It uses the new page as a cue to review Livesession activity and report findings.

Can it identify conversion blockers?

It can summarize patterns visible in the available sessions, such as hesitation or repeated navigation, for you to assess.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Notion triggers

Livesession actions

Recurring trigger

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

TriggerScheduled

List Live Sessions

Tool to list live sessions. use when you need paginated session data filtered by criteria after authentication.

ActionInstant

Webhook trigger

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

TriggerInstant

All Page Events

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

TriggerPolling

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