Review a flipbook preview when publication feedback arrives
Turn a comment on a publication page into a cue to check the Heyzine title, description, and thumbnail.
Trigger
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.
Action
Get Flipbook Social Metadata
Tool to retrieve social metadata for a specific flipbook. Use after configuring social sharing to fetch title, description, and thumbnail.
Why this helps
Feedback can arrive in a discussion thread and still leave the team unsure whether the shared preview matches the latest intent.
- Bring the current sharing preview into a feedback moment.
- Make it easier to review the exact material being discussed.
- Reduce context switching between comments and publication settings.
Setup
Build it in a few focused steps.
- 1Connect Notion and Heyzine to Notis once in the portal.
- 2Create a plain-language prompt to fetch social metadata for the flipbook referenced by a publication page when it receives a comment.
- 3Choose the Notion Comment Created trigger and scope it to the relevant page if appropriate; select a reporting channel.
- 4Test by adding one real comment to a publication page with a Heyzine flipbook reference.
Questions about this workflow
Does the comment update the metadata?
No. This workflow retrieves social metadata so it can be reviewed.
What does comment triggering require?
The Notion connection needs the Read comments capability, and it may need to be re-authorized after that capability is enabled.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Heyzine. A trigger fires from one place; an action lands in another.
Notion triggers
Heyzine actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Flipbook Link
Tool to create a direct flipbook link. Use when you have a document URL and want to convert it to a flipbook.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Flipbook Asynchronously
Tool to create a flipbook asynchronously. Use when converting large documents off-thread; poll for updates on conversion state.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Flipbook Sync
Tool to convert a PDF, DOCX, or PPTX into a flipbook synchronously via REST API. Use when you need immediate flipbook URLs from a direct file link.
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.
Delete Flipbook
Tool to delete a flipbook. Use when you need to permanently remove an unwanted flipbook.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get API Limits
Tool to retrieve API rate limits. Use when you need to check your current API usage and limits.
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 Flipbook Embed Code
Tool to retrieve HTML embed code for a flipbook. Use when you have a flipbook ID and need the <iframe> snippet to embed in a website.
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 Flipbook ID Tool
Tool to retrieve HTML for Flipbook ID tool. Use when you need to fetch the ID input tool page HTML for a specific flipbook.
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 Flipbook List
Tool to retrieve all flipbooks. Use when you need to list every flipbook for the authenticated account.
Connect any two apps with Notis in the middle.
Notion and Heyzine, 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 Heyzine.