Automatically sync VIP status to Userlist daily
Mark a customer as VIP in Notion and Notis syncs it to Userlist every morning. VIP emails go out immediately, support gets notified, special treatment triggers.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
VIP status changes in Notion don't reach Userlist for days, so VIPs miss special treatment and are on the same email list as everyone else.
- VIPs always get special email treatment without manual intervention
- Support team knows who's VIP before they reach out
- Spot VIP upsell opportunities automatically
- Separate VIP email cadence from standard campaigns
Setup
Build it in a few focused steps.
- 1Connect Notion and Userlist to Notis.
- 2Tell Notis: 'Every day at 8am, check for VIP-marked customers in Notion and sync them to Userlist.' Or set this up via the portal.
- 3Select 'Schedule' as your trigger and choose daily at your preferred time.
- 4Specify the Notion database and VIP flag field to watch.
- 5Test by manually triggering a sync to verify VIP customers appear with the VIP tag in Userlist.
Questions about this workflow
What makes a customer VIP in your model?
Define it yourself. ARR above $100k, strategic partners, beta customers, or any criteria that matters. Mark them in Notion and Notis syncs the flag.
Can I have multiple VIP tiers?
Yes. Use different field values (VIP, Enterprise, Strategic) and create separate segments in Userlist for each tier.
How should I use VIP tags in Userlist?
Create a VIP email list and send different, more personalized campaigns. Add VIP tags to campaigns so the sales team sees them.
What if a customer loses VIP status?
Update their status in Notion and the daily sync removes the VIP tag from Userlist the next morning.
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
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
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.
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.
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.
New Page
Triggers when a new page is added to a Notion database.
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Connect any two apps with Notis in the middle.
Not just Notion and Userlist. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Userlist.