See visit history when a prospect enters Notion
Start prospect review with the Leadfeeder activity already gathered, instead of switching tabs to reconstruct the trail.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Get All Visits
Tool to retrieve all visits for a specific lead. use when you need detailed visit history for a lead, optionally filtered by date range.
Why this helps
A newly added prospect can sit untouched while someone hunts for prior website activity.
- Brings recent browsing activity into the first prospect review.
- Reduces the number of manual lookups during lead qualification.
- Makes it easier to decide what deserves attention next.
Setup
Build it in a few focused steps.
- 1Connect Notion and Leadfeeder to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to review Leadfeeder activity for each new Notion prospect.
- 3Write one plain-language instruction that asks for visit history for the matching Leadfeeder lead and a short summary.
- 4Select the Notion New Page trigger and choose where run reports should go.
- 5Test with a new prospect that has a corresponding Leadfeeder lead.
Questions about this workflow
Can the automation find a matching lead from any prospect page?
The prompt should explain how Notis can identify the corresponding Leadfeeder lead from the available context. Test with a real example.
Can it create a follow-up in Leadfeeder?
No. This workflow retrieves visit history and summarizes it; the selected action does not create follow-ups.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Leadfeeder. A trigger fires from one place; an action lands in another.
Notion triggers
Leadfeeder actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Accounts
Tool to retrieve a list of accounts the user has access to. use when you need to discover all available leadfeeder accounts after authentication.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get All Visits
Tool to retrieve all visits for a specific lead. use when you need detailed visit history for a lead, optionally filtered by date range.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Company Info by IP
Tool to retrieve company information based on an ip address. use when you need to enrich an ip and obtain its company profile. returns 404 if no match is found.
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.
Get Custom Feeds
Tool to retrieve a list of custom feeds for a specific account. use after confirming the account id to list all its custom feed configurations.
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 Leadfeeder, 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 Leadfeeder.