Partnership Opportunity Research Workflow
Evaluate partnership fit in seconds. Auto-enrich LinkedIn profiles the moment you flag a partnership opportunity.
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
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
Founders lose momentum evaluating partnerships because manual LinkedIn research breaks their focus and flow.
- Partnership fit assessed instantly
- Key stakeholder backgrounds automated
- No research slowdown for founders
- Better partnership decisions
Setup
Build it in a few focused steps.
- 1Ensure Notion and Aeroleads are connected to Notis.
- 2Create a new automation or ask Notis: 'Enrich partnership opportunities with LinkedIn data.'
- 3Write: 'When a partnership opportunity is flagged, get full LinkedIn details on all stakeholders and add to the Notion page.'
- 4Select 'Page Properties Updated' as the trigger and filter for partnership status changes.
- 5Test by flagging a partnership opportunity and watch the enrichment flow.
Questions about this workflow
Can I enrich multiple stakeholders at once?
Yes. In your prompt, ask Notis to enrich every LinkedIn URL on the page automatically.
What data is most useful for partnership decisions?
Job titles, company history, mutual connections, and past partnerships. Aeroleads surfaces all of these.
How long does enrichment take?
Usually within seconds. Notis will notify you when data is ready.
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.