Turn an account page update into a batched Engage update
After you refresh a Notion account page, let Notis apply the related customer updates and events together in Engage.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Batch Request
Tool to batch multiple create user, update user, and add user events operations into a single API call. Use when you need to perform multiple operations efficiently at the cost of one API request. The batch is queued for processing without immediate validation, so ensure all parameters are correct. Request size must remain under 100KB.
Why this helps
Catching up several customer records after an account review can mean repeating the same workflow many times.
- Reduce repetitive updates after account reviews.
- Handle related user updates in one batch request.
- Make review outcomes easier to carry into customer records.
Setup
Build it in a few focused steps.
- 1Connect Notion and Engage to Notis once through the portal.
- 2Create an automation in the portal or tell Notis the intended outcome in plain language.
- 3Ask Notis to batch the relevant Engage user updates and event records after the account page content changes.
- 4Choose the Notion Page Content Updated trigger for the account review page and select a channel for run reports.
- 5Test with one real account review update and inspect the resulting Engage changes.
Questions about this workflow
What can the batch action include?
Batch Request supports multiple create user, update user, and add user events operations. Describe the required operations in your instruction.
Does the batch validate each operation immediately?
The batch is queued without immediate validation, so test with a real example and keep the requested operations clear.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Engage. A trigger fires from one place; an action lands in another.
Notion triggers
Engage actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Customer to Accounts
Tool to add a customer to one or more account entities. Use when you need to associate a user with accounts and optionally assign roles.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add User to Lists
Tool to add a Customer or Account to one or more Lists in Engage.so. Use when you need to subscribe a user to specific lists for targeted messaging.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Archive List
Tool to archive a List in Engage. Use when you want to prevent new subscribers from being added to a list. Existing subscribers will not be affected.
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.
Archive User
Tool to archive a user in Engage. Use when you need to deactivate a user account while preserving all historical data. The user will stop being active and all engagement and events for the user will be stopped, but all messages, logs, and related data will be preserved.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Convert User Type
Tool to convert a user between Customer and Account entity types. Use when you need to change a customer to an account or vice versa.
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.
Create List
Tool to create a new List in Engage for organizing subscribers. Use when you need to set up a new list for managing contacts or subscribers.
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.
Create User
Tool to create a new user (Customer or Account) in Engage. Use when you need to add a user with optional metadata, device tokens, or list subscriptions.
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.
Delete Subscriber From List
Tool to remove a subscriber from a List entirely (different from unsubscribing). Use when you need to completely delete a subscriber's association with a specific list.
Connect any two apps with Notis in the middle.
Notion and Engage, 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 Engage.