Open a CraftMyPDF editor session for an updated draft
Connect the latest draft edits to a concrete next step: opening the document editor to review the finished layout.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Create Editor Session
Tool to create an embeddable editor session URL for a template. Use when you need to embed the PDF editor for a specific template.
Why this helps
A draft can be ready for visual formatting but still sit untouched because the next person has to locate the right template and editor.
- Create an editor session when draft content changes.
- Help a reviewer move directly from updated copy to document layout.
- Reduce the chance that a ready draft stalls before formatting.
Setup
Build it in a few focused steps.
- 1Connect Notion and CraftMyPDF to Notis once in the portal.
- 2Create an automation and describe which draft edits should open an editor session and which template to use.
- 3Choose Page Content Updated for the draft page or data source and select a report channel.
- 4Test with one draft edit and open the generated editor session URL.
Questions about this workflow
Does this detect every keystroke?
Notion aggregates page content edits within a short window, typically around 60 seconds.
Can it create a completed PDF without review?
No. The action creates an editor session URL for someone to review and finish.
Can I limit it to a particular draft?
Scope Page Content Updated to a specific page or data source and describe the intended draft behavior in the prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Craftmypdf. A trigger fires from one place; an action lands in another.
Notion triggers
Craftmypdf actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Editor Session
Tool to create an embeddable editor session URL for a template. Use when you need to embed the PDF editor for a specific template.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create PDF Asynchronously
Tool to queue asynchronous PDF generation via webhook. Use when you need to generate a PDF in the background and receive the result via a webhook.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List PDF Templates
Tool to retrieve a paginated list of PDF templates. Use when you need to browse available templates before generating a PDF.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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.
Connect any two apps with Notis in the middle.
Notion and Craftmypdf, 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 Craftmypdf.