Resolve prospect profiles before outreach
Mark an outreach list ready in Notion and use Icypeas to find the prospects' public profile URLs in bulk.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Find Profile URLs Bulk
Tool to perform bulk search for profile URLs. Use when you need to resolve multiple prospects' profile URLs at once.
Why this helps
Profile research is repetitive, making it easy for an approved outreach list to lose momentum before contact.
- Start profile research when an outreach list is ready.
- Resolve multiple profile URLs through one bulk search.
- Keep approval and prospect research status connected.
Setup
Build it in a few focused steps.
- 1Connect Notion and Icypeas to Notis once in the portal.
- 2Create a new automation in the portal or ask Notis conversationally.
- 3Write one plain-language instruction asking Notis to start an Icypeas bulk profile URL search when an outreach record is marked approved.
- 4Select the Notion Page Properties Updated trigger and choose where run reports go.
- 5Test with one real approved outreach entry and inspect the Icypeas search.
Questions about this workflow
When should I use bulk profile URL search?
Use it when multiple prospects need profile URL discovery at once.
Does approval automatically mean a message is sent?
No. This workflow searches for profile URLs and does not send outreach.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Icypeas. A trigger fires from one place; an action lands in another.
Notion triggers
Icypeas actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Bulk Email Search
Tool to start a bulk email search job. Use when you have up to 5000 names and domains to batch-find emails via the ICYPEAS bulk-search endpoint.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Check Search Progress
Tool to check the progress of a search by its ID. Use after initiating a single or bulk search to poll for its processing status.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Domain Scan
Tool to scan a domain for role-based email addresses. Use when you need to discover all role-based emails for a specific domain.
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.
Fetch Bulk Search Info
Tool to fetch information about bulk search files. Use when you need status and pagination details after initiating bulk search operations.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Fetch Subscription Information
Tool to fetch subscription and credit info. Use after obtaining a valid API key.
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.
Find Companies
Tool to search companies in Icypeas database. Use when you need to find companies matching filters like industry, location, or headcount.
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.
Find Company URL
Tool to find a single company profile URL using a company name or domain. Use when you need to initiate a profile-URL search for a given company identifier.
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.
Find People
Tool to search for people in the leads database. Use when you need to filter people by name, title, company, and other attributes.
Connect any two apps with Notis in the middle.
Notion and Icypeas, 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 Icypeas.