Automatically link customer contacts to companies in Userlist
Add a new contact as a subpage under a customer in Notion and Notis automatically links them to that company in Userlist. Your contact list stays in sync across tools.
Trigger
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
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 information scattered across Notion subpages isn't connected to company records in Userlist, making it hard to find the right contact when you need to reach out.
- Find every contact for a customer instantly without hunting through Notion subpages
- Email the right person at each company automatically through Userlist's contact list
- Track decision makers and stakeholders without manual entry
- Onboard new team members at customer accounts without forgotten contacts
Setup
Build it in a few focused steps.
- 1Connect Notion and Userlist to Notis.
- 2Tell Notis: 'When a new subpage is added under a customer page in Notion, link that contact to the customer company in Userlist.' Or set this up in the portal.
- 3Select 'Page Added to Page' as your trigger and choose the Notion parent page or database.
- 4Pick your notification channel.
- 5Test by adding a new contact subpage under a customer and verify it links in Userlist within 60 seconds.
Questions about this workflow
What contact information gets synced?
Name, title, email, and phone from the Notion subpage. Notis pulls whatever fields you've set up on the contact template.
What if a contact works at multiple companies?
Set up your Notion structure so each contact is linked to their primary company. For secondary roles, you can create a separate manual note in Userlist.
Does this create new contacts in Userlist?
Yes, it creates the contact record and links them to the company. If the contact already exists, Notis updates their company assignment.
Can I sync contact changes (like title updates)?
Yes. Create a separate automation watching for page content or property updates on your contact subpages.
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.