Give every Notion feedback page a Gleap follow-up
A suggestion captured in Notion can become a trackable Gleap ticket without interrupting your current work.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Create a new ticket
Tool to create a new ticket. Use when you have ticket details ready to open a support ticket.
Why this helps
Feedback written down for later can disappear beneath newer tasks when nobody turns it into a follow-up item.
- Give customer suggestions a trackable destination
- Reduce the gap between capture and triage
- Spend less time re-entering feedback
Setup
Build it in a few focused steps.
- 1Connect Notion and Gleap to Notis once through the portal.
- 2Create an automation or ask Notis to create a Gleap ticket whenever you add a feedback page in Notion.
- 3Choose the Notion Page Created trigger and describe which feedback pages should lead to tickets.
- 4Choose a run-report channel and test with one real feedback page.
Questions about this workflow
Can the prompt focus on feedback pages?
Yes. State in plain language that the automation should create tickets for pages in your feedback area or with feedback-related content.
Will it create a ticket for every page in Notion?
The trigger can be scoped to a parent page or data source where supported. Describe the intended feedback pages in the automation instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Gleap. A trigger fires from one place; an action lands in another.
Notion triggers
Gleap actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Archive a Ticket
Tool to archive a ticket. Use after confirming the ticket ID and that the ticket is resolved. Call when moving tickets to history.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create a Collection
Tool to create a help center collection. Use when adding a new organizational grouping in your Help Center.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create a new chat message
Tool to create a new chat message. Use when sending a message in an active chat session.
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 a new team
Tool to create a new team. Use when you have team details ready and want to assign tickets among members.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create a new ticket
Tool to create a new ticket. Use when you have ticket details ready to open a support ticket.
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.
Delete a User from a Project
Tool to remove a user from a project. Use when you need to revoke a user's access by their 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.
Get a Checklist
Tool to retrieve a specific engagement checklist by its ID. Use after obtaining a valid checklistId.
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.
Get a Collection
Tool to retrieve a help center collection by ID. Use when you need to fetch specific collection details by its ID.
Connect any two apps with Notis in the middle.
Notion and Gleap, 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 Gleap.