Start a PDF editor session from a new Notion record
Move from capturing a need in Notion to a ready-to-open editor session for the right document template.
Trigger
New Page
Triggers when a new page is added to a Notion database.
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 record that needs a custom document can get stuck while someone searches for the right template and editor entry point.
- Create an editor session URL for a chosen template after a new record arrives.
- Reduce the steps between noting a document need and opening its editor.
- Give a repeatable starting point to review and finish a PDF.
Setup
Build it in a few focused steps.
- 1Connect Notion and CraftMyPDF to Notis once in the portal.
- 2Create an automation and specify in plain language which template should open for a new document record.
- 3Choose New Page for the relevant Notion database and select a channel for run reports.
- 4Test with one real record and open the generated editor session URL.
Questions about this workflow
Does this generate a finished PDF?
No. Create Editor Session returns an embeddable editor session URL for a template.
Can a person edit the document before completion?
Yes. The editor session is intended to open the PDF editor for the selected template.
How should I choose a template?
Name the intended template in your plain-language instruction. You can use the template list action separately to browse options.
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.