Respect customer preferences with automatic sync from Notion
Track communication preferences in Notion and Notis syncs them to Userlist instantly. Respect opt-in choices, contact method preferences, and frequency limits.
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
Push User-Company Relationship
Tool to create or update a relationship between a user and a company in userlist. use after confirming valid user and company identifiers.
Why this helps
Contact preferences and communication choices trapped in Notion mean Userlist sends emails to customers who don't want them, risking unsubscribes and brand damage.
- Respect customer communication preferences automatically
- Reduce unsubscribe rates by honoring opt-in choices
- Send via preferred channel (email, Slack, in-app, etc.) automatically
- Comply with preference center requirements without manual management
Setup
Build it in a few focused steps.
- 1Connect Notion and Userlist to Notis.
- 2Tell Notis: 'When a customer's communication preferences change in Notion, update their preferences in Userlist.' Or set this up via the portal.
- 3Select 'Page Properties Updated' and choose your Notion database and preference fields (email frequency, contact method, do not contact, etc.).
- 4Describe the preference update in one plain-language instruction, such as updating email frequency, contact method, or do-not-contact settings when the Notion page changes.
- 5Test by changing a customer's preferences in Notion and verify Userlist respects the new settings within 30 seconds.
Questions about this workflow
What preferences should I track?
Email frequency (daily, weekly, monthly, never), preferred contact method (email, SMS, Slack), do-not-contact flags, and any industry-specific preferences.
Can customers override preferences in Userlist?
Yes. Userlist-set preferences take precedence. Notion is your source of truth, but customers can adjust in Userlist too.
How do I ensure compliance?
Mark any hard do-not-contact flags in both Notion and Userlist, and create automations to never email those customers.
Can I offer a preference center?
Yes. Once preferences sync to Userlist, let customers update their own settings. Sync changes back to Notion if needed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Userlist. A trigger fires from one place; an action lands in another.
Notion triggers
Userlist actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Company from Userlist
Tool to delete a company from userlist. use when you need to remove a company by its unique identifier after verifying it.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Push User-Company Relationship
Tool to create or update a relationship between a user and a company in userlist. use after confirming valid user and company identifiers.
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 Userlist, 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 Userlist.