Sync new customers from Notion directly into Userlist
When you capture a new customer in Notion, Notis automatically creates their company record in Userlist. No manual entry, no duplicates, no forgotten customers.
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
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
Manually copying customer information from Notion to Userlist creates duplication, introduces errors, and leads to customers who slip through onboarding cracks.
- New customers appear in Userlist immediately, ready for email campaigns
- No manual copying means fewer errors and typos in customer records
- Sales and support teams stay in sync about who's been onboarded
- Reduce time spent on data admin work so you can focus on growth
Setup
Build it in a few focused steps.
- 1Connect your Notion workspace and Userlist account to Notis through the portal (done once, then reused for all automations).
- 2Ask Notis: 'When a new customer page is created in Notion, create or update their company record in Userlist.' Or create this in the portal under Automations > New Automation.
- 3Select 'Page Created' as the trigger and choose the Notion database where you store customers.
- 4Pick your preferred channel (email, Slack, etc.) to receive run notifications.
- 5Test it: add one new customer to Notion and verify they appear in Userlist within seconds.
Questions about this workflow
What customer information gets synced?
The automation syncs the company name, company ID, and any Notion properties you set up (like industry, location, contact name). Notis interprets the Notion data and maps it to Userlist's company fields intelligently.
What if I already have customers in Userlist?
This automation only fires for newly created Notion pages going forward. Existing customers won't be synced. You can run a separate historical sync if needed.
Can I customize which customers get synced?
Yes. Tell Notis to scope the automation to a specific Notion database or add a filter like 'only sync customers marked as active' by adjusting your automation prompt.
How long does the sync take?
Usually under 30 seconds from when you create the Notion page. Notion events can have a short aggregation delay (60 seconds typical).
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.