Refresh proposal PDFs when the record changes
When a proposal moves forward, make the current version easy to send without rebuilding it by hand.
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
Convert HTML to PDF
Tool to convert HTML to a PDF document. Use when you need to generate a PDF from raw HTML. Returns raw PDF bytes suitable for download or storage.
Why this helps
A changed proposal can sit in Notion while the shareable version still reflects old details.
- Create a fresh proposal PDF after a relevant record update.
- Reduce the chance of sending an outdated version.
- Keep proposal prep moving when attention is already on the next task.
Setup
Build it in a few focused steps.
- 1Connect Notion and Customjs to Notis once through the portal.
- 2Create an automation with one instruction describing how an updated proposal page should become a PDF.
- 3Select Page Properties Updated for the proposals data source, choose a run-report channel, and test on one real proposal.
Questions about this workflow
Does it create a PDF after every property update?
The trigger runs on page property updates. Describe in the instruction which updates matter and what the PDF should contain.
Can the PDF use the latest page details?
Tell Notis to use the updated proposal page as the source for the generated PDF.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Customjs. A trigger fires from one place; an action lands in another.
Notion triggers
Customjs actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Authenticate CustomJS API Key
Tool to authenticate a CustomJS API key. Use when verifying a user's API key before making further requests.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Convert HTML to PDF
Tool to convert HTML to a PDF document. Use when you need to generate a PDF from raw HTML. Returns raw PDF bytes suitable for download or storage.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Convert HTML to PNG
Tool to convert HTML string to PNG image. Use when you need a PNG from HTML after preparing your markup.
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.
Capture webpage screenshot
Tool to capture a screenshot of a webpage. Use when you need a visual snapshot of a URL.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Merge multiple PDFs into one
Tool to merge multiple PDF files into a single PDF. Use when you have multiple PDF URLs and want one combined PDF.
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.
Run Puppeteer Script
Tool to run a Puppeteer script and capture a screenshot. Use when automating headless browser tasks and needing a PNG output. Use after confirming the script logic.
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 Customjs, 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 Customjs.