Find work email contacts for new partner prospects
Add a potential partner to Notion and let ContactOut check their LinkedIn profile for work email contact details.
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
LinkedIn Contacts Only (Work Email)
Contacts only, no profile body, from a LinkedIn URL; bills work email credits.
Why this helps
Partnership exploration competes with delivery work, so promising introductions can wait too long for basic contact research.
- Move from partner idea to contact research sooner.
- Reduce the manual steps needed to start a conversation.
- Keep new partnership leads from being buried in notes.
Setup
Build it in a few focused steps.
- 1Connect Notion and ContactOut to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to set it up in plain language.
- 3Give one instruction to find work email contacts for each new partner prospect using the LinkedIn URL in context.
- 4Select Notion Page Created, choose a run-report channel, and test with one real partner prospect.
Questions about this workflow
Does the action include profile details?
This action returns contacts only, without the profile body, and bills work email credits.
What should a new prospect page include?
Include a LinkedIn URL so ContactOut can look up work email contact details.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to ContactOut. A trigger fires from one place; an action lands in another.
Notion triggers
ContactOut actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
LinkedIn Contacts Only (Work Email)
Contacts only, no profile body, from a LinkedIn URL; bills work email credits.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Check Phone Availability
Check whether a phone number exists for a LinkedIn profile; consumes no credits.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Verify Email
Check one email address's deliverability; a definitive verdict bills one verifier credit.
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.
Enrich Person (Personal Email)
Match a person by any identifier mix; contact reveal bills personal email credits.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
LinkedIn Full Profile + Contacts (Work Email)
Full LinkedIn profile plus contacts from a profile URL; bills work email credits.
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 Companies
Find companies by size, industry, location, revenue, technologies; bills search credits.
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 ContactOut, 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 ContactOut.