Automatically track new hires at your customers
Document a new hire at a customer in Notion and Notis adds them to their company in Userlist. Track headcount growth, identify upsell opportunities.
Trigger
New Page
Triggers when a new page is added to a Notion database.
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
New hires at customer companies don't get added to Userlist automatically, so you miss growth signals and don't expand to new stakeholders.
- Spot customer growth signals when headcount expands
- Automatically contact new hires with onboarding sequences
- Upsell larger deployments when companies grow
- Track customer organization changes without manual updates
Setup
Build it in a few focused steps.
- 1Connect Notion and Userlist to Notis.
- 2Tell Notis: 'When a new employee page is added to a customer's hiring list in Notion, add them to that customer company in Userlist.' Or use the portal.
- 3Select 'New Page' as your trigger and choose the Notion database where you track customer employees.
- 4Specify which field links employees to their company (e.g., Company Name, Company ID).
- 5Test by adding a new employee to a customer's Notion section and verify they appear in Userlist within 30 seconds.
Questions about this workflow
What employee information gets added?
Name, title, email, and any other fields on your Notion employee template. Notis syncs whatever you track.
How do I use this to identify upsell opportunities?
Track headcount growth and trigger expansion conversations when companies hire more people. They probably need more seats or deployment.
What if an employee switches companies?
Update their company field in Notion and Notis moves their record to the new company in Userlist.
Can I send a welcome email to new customer employees?
Yes. Once they're added to their company in Userlist, set up an automation to send them a tailored welcome sequence.
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.