Conference Attendee LinkedIn Profiling
Met someone at a conference? Automatically pull their LinkedIn profile so you can follow up with real context.
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
Hundreds of new connections post-conference feel like a blur. Founders can't remember enough about each person to make meaningful follow-up.
- Instant context for every new contact
- Follow-up messages feel personal
- No more blank stares at new connections
- Build genuine relationships at scale
Setup
Build it in a few focused steps.
- 1Connect Notion and Aeroleads to Notis.
- 2Create an automation: 'When I add a conference attendee, enrich their LinkedIn profile automatically.'
- 3Write the prompt: 'Extract attendee name or LinkedIn URL, fetch full profile from Aeroleads, add company, role, and bio to Notion.'
- 4Use 'Page Created' trigger for your conference attendees database.
- 5Test by copying in a few attendees and watching enrichment populate their details.
Questions about this workflow
How do I add attendees quickly?
Paste a list of names into Notion, or use a form. Notis will enrich each name automatically.
Can I see mutual connections?
Aeroleads surfaces mutual connections from LinkedIn, helping you find warm intro paths.
What's the best follow-up timeframe?
Research shows 24-48 hours. Set a Notis reminder to follow up after enrichment completes.
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.