Look up a prospect as soon as their Notion page appears
Capture a name or profile in Notion and have Notis search LeadIQ for a matching person while the context is fresh.
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
Search People
Search for individual contacts by name, company (past and present), LinkedIn profile, email, or phone number. Use when you need to find people based on identifying information. Returns comprehensive contact data including work/personal emails, phones, employment history, education, and social profiles.
Why this helps
A promising contact gets captured in notes, but the lookup needed to qualify them remains an easy task to forget.
- Keep initial contact research connected to the page that captured the lead.
- Use available identifying details to find a matching LeadIQ profile.
- Reduce the mental overhead of maintaining a separate lookup queue.
Setup
Build it in a few focused steps.
- 1Connect Notion and LeadIQ to Notis once through the portal.
- 2Create an automation in the portal or ask Notis in any connected channel.
- 3Give Notis one plain-language instruction to search LeadIQ for the person described in each new prospect page and report the best matching profile.
- 4Select the Notion Page Created trigger, scope it to the intended parent page if useful, and choose a run-report channel.
- 5Test with one real prospect page and check that the result matches the intended person.
Questions about this workflow
What information can Notis use for the lookup?
The prompt can ask Notis to use identifying details available in the Notion page, such as the person's name, company, or profile URL.
What happens if there is no clear match?
Ask Notis in the prompt to report uncertainty or missing matches so you can review them rather than treating a guess as confirmed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to LeadIQ. A trigger fires from one place; an action lands in another.
Notion triggers
LeadIQ actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Abandon Import Batch
Abandon a contact tracking import batch that is no longer needed. Use when you need to cancel or stop an ongoing import batch operation.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Account Details
Retrieve current user's account information including plans, billing cycles, and credit usage. Use to check available API credits, billing status, and data visibility settings before making data queries.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Contact Tracking Balance
Tool to check the remaining balance of contact tracking credits available for the account. Use when you need to verify how many contact tracking credits are left.
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 Usage Statistics
Tool to retrieve API usage statistics and credit consumption for the current LeadIQ account. Use when you need to check credit usage, remaining capacity, or billing information.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Search Company
Tool to search for companies by name, domain, LinkedIn URL, or other identifying information. Use when you need to find companies matching specific criteria. Returns detailed company information including employee count, industry, location, and social profiles.
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.
Search Grouped Advanced
Tool to search for people by job title, seniority, role, company size, and location with results grouped by company. Returns companies with matching people nested under each company for account-based prospecting. Use when you need to find contacts at companies matching specific criteria.
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.
Search People
Search for individual contacts by name, company (past and present), LinkedIn profile, email, or phone number. Use when you need to find people based on identifying information. Returns comprehensive contact data including work/personal emails, phones, employment history, education, and social profiles.
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.
Flat Advanced Search
Tool to search for people using advanced filters by job title, seniority, role, company size, location, and more. Returns a flat list of individual contacts unorganized by company.
Connect any two apps with Notis in the middle.
Notion and LeadIQ, 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 LeadIQ.