Connect external tools to update customers in Userlist via webhook
External tool detects something important? Post a webhook and Notis updates that customer in Userlist instantly. Real-time integration without manual steps.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
External systems can't talk to Userlist directly, so important customer flags and status changes don't reach your email tool.
- Real-time customer flags from external systems reach Userlist instantly
- Trigger campaigns based on events outside Notion
- Build complex automations that span your entire toolchain
- No code needed - just set up the webhook URL and send JSON
Setup
Build it in a few focused steps.
- 1Connect Userlist to Notis.
- 2Tell Notis: 'When you receive a webhook about a customer, update or tag them in Userlist.' Or set this up via the portal.
- 3Select 'Webhook' as your trigger type. Notis generates a unique webhook URL for this automation.
- 4Provide that URL to your external tool (support tool, analytics platform, billing system, etc.).
- 5Test by having the external tool send a sample webhook payload and verify the customer updates in Userlist.
Questions about this workflow
What should the webhook JSON look like?
Keep it simple: company_id, company_name, field_name, and new_value. Notis guides you on the exact format when you set up the webhook.
Can I send webhooks from multiple external tools?
Yes. Create separate automations for each tool or send them all to the same webhook URL if they use compatible formats.
What if I need to sync customer data that Notion doesn't track?
Perfect use case for webhooks. Any external system (billing, support, analytics) can send data directly to Userlist.
How do I monitor webhook delivery?
Notis logs all webhook events. Check the automation run history to see what was received and processed.
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.