Prepare interview contacts without extra lookup work
Add the people you want to learn from, then let Bettercontact help find the right contact details.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Enrich Leads
Tool to create a lead enrichment request for work emails and direct phone numbers. Uses waterfall enrichment across multiple data providers for higher accuracy. Supports batches of 1-100 leads.
Why this helps
Finding contact information can slow down customer discovery before the first conversation is even scheduled.
- Reduces admin before customer interviews
- Keeps the interview list with research context
- Makes it easier to act on a discovery plan
Setup
Build it in a few focused steps.
- 1Connect Notion and Bettercontact to Notis once.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Tell Notis in one instruction to request enrichment for the interview contacts explicitly listed on a new interview-list page.
- 4Select Notion New Page as the trigger and choose where run reports should arrive.
- 5Test by creating one real interview list with a small set of contacts.
Questions about this workflow
Does Bettercontact schedule the interviews?
No. This action requests contact enrichment; scheduling is outside the described Bettercontact action.
Can I limit who is enriched?
Yes. Describe which listed people should be included in the plain-language instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Bettercontact. A trigger fires from one place; an action lands in another.
Notion triggers
Bettercontact actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Credits Balance
Tool to check the remaining credits balance for a BetterContact account. Use when you need to verify available credits before making API requests that consume credits.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Lead Finder Search
Tool to create a new Lead Finder search to discover leads based on company and people criteria. Use when you need to find prospects matching specific job titles, departments, seniority, company size, industry, or technology stack.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Enrich Leads
Tool to create a lead enrichment request for work emails and direct phone numbers. Uses waterfall enrichment across multiple data providers for higher accuracy. Supports batches of 1-100 leads.
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.
Get Enrichment Results
Tool to retrieve enrichment results for a specific request ID. Use when you need to check the status and get enriched lead data including email addresses, contact information, and summary statistics for a submitted enrichment request.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Lead Finder Results
Tool to retrieve results from a submitted Lead Finder search. Returns comprehensive lead and company data including contact information, LinkedIn profiles, job titles, company details, and enrichment data.
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.
Connect any two apps with Notis in the middle.
Notion and Bettercontact, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Bettercontact.