Cold Outbound Prospect Enrichment Workflow
Personalized cold outreach works. Automatically enrich prospects with LinkedIn data for compelling first messages.
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
Get Details From LinkedIn URL
Tool to retrieve detailed information about a prospect using their linkedin profile url. use after confirming you have a valid public linkedin url, to enrich lead profiles with additional details.
Why this helps
Writing personalized cold emails takes forever because founders must manually research each prospect's background.
- Cold email response rates improve drastically
- Personalization at scale is now possible
- Founder time freed up for actual selling
- Better qualified prospect conversations
Setup
Build it in a few focused steps.
- 1Connect Notion and Aeroleads to Notis.
- 2Create an automation: 'Enrich every cold prospect I add with LinkedIn details for personalization.'
- 3Prompt: 'Extract prospect LinkedIn URL, get full profile and company context from Aeroleads, add key insights for personalized outreach to Notion.'
- 4Set trigger to 'Page Created' in your cold outbound database.
- 5Test by adding a prospect and using the enriched details to draft a personalized email.
Questions about this workflow
How much personalization is enough?
Reference their recent role change, mutual connection, or company news. Aeroleads surfaces all of this.
Should I mention mutual connections?
Absolutely. Warm introductions work far better. Aeroleads shows mutual LinkedIn connections.
What if they reject me the first time?
Re-check their LinkedIn in 6 months. Career changes open new conversation angles.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Aeroleads. A trigger fires from one place; an action lands in another.
Notion triggers
Aeroleads actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Details From LinkedIn URL
Tool to retrieve detailed information about a prospect using their linkedin profile url. use after confirming you have a valid public linkedin url, to enrich lead profiles with additional details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
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.
Connect any two apps with Notis in the middle.
Notion and Aeroleads, 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 Aeroleads.