Move new Notion pages into your SEO workflow
When a new Notion page is created, let Notis import its content into Neuronwriter so the SEO editing step is easier to begin.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Import Content
Tool to import content into the editor. use when updating editor content via html or url.
Why this helps
New writing may be ready for SEO work, but starting that work requires remembering another tool and another transfer.
- Make new writing easier to pick up in the SEO editor.
- Avoid a separate copy-and-paste routine.
- Reduce the number of small handoffs to remember.
Setup
Build it in a few focused steps.
- 1Connect Notion and Neuronwriter to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3In one plain-language instruction, tell Notis which new pages to import into Neuronwriter and what content to include.
- 4Choose the Notion Page Created trigger and a channel for run reports.
- 5Test by creating one real page and checking Neuronwriter.
Questions about this workflow
Can I scope this to new pages under a parent page?
The Page Created trigger can be scoped to a parent page for new sub-pages.
Does this trigger apply to database rows?
For a new page added to a database, use the New Page trigger.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Neuronwriter. A trigger fires from one place; an action lands in another.
Notion triggers
Neuronwriter actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Import Content
Tool to import content into the editor. use when updating editor content via html or url.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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 Neuronwriter, 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 Neuronwriter.