Refresh client brief PDFs when Notion details change
Keep the version you share aligned with the client information you maintain in Notion.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are 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 property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
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.
Why this helps
Client details evolve, but the PDF used by a collaborator can quietly fall behind unless someone remembers to refresh it.
- Generate a fresh brief when client properties change.
- Reduce the risk of sharing old contact or project information.
- Make client handoffs easier to prepare and maintain.
Setup
Build it in a few focused steps.
- 1Connect Notion and CraftMyPDF to Notis once in the portal.
- 2Create an automation and describe the client brief update in one plain-language prompt.
- 3Choose Page Properties Updated for the client data source and select a channel for run reports.
- 4Test with one client record update and compare the generated PDF with the source.
Questions about this workflow
Can the automation respond only to certain changed properties?
Notion includes updated-property details in the event, and you can describe the relevant changes in the prompt.
Will this update the existing PDF?
The configured action generates a PDF asynchronously. Whether an earlier file is replaced depends on the tools and instructions used.
What makes this useful for handoffs?
A refreshed brief can gather current client context into one document for the next person picking up the work.
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.