Make new databases ready for collaborators
A new database can trigger a simple setup checklist before it becomes another place to track work.
Trigger
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.
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
New databases often lack the small setup steps that help everyone use them consistently.
- Create a repeatable checklist for new database containers.
- Help remember the setup and introduction steps for shared tracking spaces.
- Make database launches less dependent on working memory.
Setup
Build it in a few focused steps.
- 1Connect Notion and Customjs to Notis once in the portal.
- 2Create an automation with one instruction describing the checklist PDF to generate for each new database.
- 3Choose Database Created, select a channel for run reports, and test with a real database creation.
Questions about this workflow
Does this detect a new data source in an existing database?
No. Database Created is for a new database container; use the separate data source event for a new data source.
Can the checklist be customized?
Describe the launch steps you want included in the automation instruction.
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.