Turn a customer intake page into an Engage user
Capture an intake in Notion and let Notis prepare the Engage profile while you focus on onboarding.
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
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.
Why this helps
Transcribing intake details creates extra work at the moment when a new customer needs a smooth start.
- Reduce onboarding admin.
- Keep customer setup moving after intake.
- Make the Engage profile available for follow-up.
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 what you want in plain language.
- 3Ask Notis to create an Engage user from each new customer intake page using the relevant details.
- 4Choose the Notion Page Created trigger for the intake page or database and select a channel for run reports.
- 5Test with one real intake page and review the Engage profile.
Questions about this workflow
What if the intake page is a database row?
Use the New Page trigger for a database row, or Page Created for a page-based intake flow.
Can the new profile include useful attributes?
Describe the details to include in your instruction.
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.