Capture booked demo milestones from Notion in LeadBoxer
Record a demo booking once in Notion and let Notis add the activity to LeadBoxer, making the handoff into follow-up review less fragile.
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
Log Server-Side Event
Tool to track server-side events in LeadBoxer. Use when tracking backend events, page views, or custom activities from your server. This endpoint supports tracking user interactions, conversions, and other activities that occur on the server-side.
Why this helps
A booked demo can be recorded in a planning database but disappear from the engagement timeline your team uses to prepare.
- Keep demo milestones visible with lead activity.
- Reduce context switching between planning and analytics.
- Support more prepared follow-up.
Setup
Build it in a few focused steps.
- 1Connect Notion and LeadBoxer to Notis once in the portal.
- 2Create an automation in the portal or tell Notis to log a LeadBoxer event when a lead is marked as having a booked demo.
- 3Choose the Notion Page Properties Updated trigger for the relevant lead data source.
- 4Choose where run reports should go and test by marking one test lead as booked.
Questions about this workflow
What if the lead record changes for another reason?
State clearly in the prompt that the event applies when the record indicates a booked demo.
Does this send a calendar invitation?
No. It logs a milestone in LeadBoxer after the Notion record reflects the booking.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to LeadBoxer. A trigger fires from one place; an action lands in another.
Notion triggers
LeadBoxer actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add or Update Lead Tags
Tool to add or update lead tags in LeadBoxer. Use when you need to manage lead tags by adding new tags, removing specific tags, or overwriting all existing tags for a specified user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Custom Tracking Domain
Tool to delete a custom tracking domain entry for a dataset. Use when you need to remove a specific custom tracking domain (CTD) associated with a dataset in LeadBoxer.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Events
Tool to fetch events for specified sessions from LeadBoxer. Use when you need to retrieve behavioral data including pageviews, clicks, form submissions, email interactions, and custom events. Events can be filtered by session ID, email, user ID, or segment/smartlist IDs.
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 Lead Score Formula
Tool to fetch the lead score formula for a specific dataset. Use when you need to understand how lead scores are calculated for records in a dataset. The formula defines scoring based on criteria types: Range (number ranges), Match (exact values), Exists (presence of values), and Boost (event-based scoring).
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Sessions
Tool to fetch sessions for a specified lead ID from LeadBoxer. Use when you need to retrieve session data for a user, with optional filtering by email, user ID, Smartlist ID, or segment ID. A session represents a single visit to the site, and users can have multiple sessions over time.
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.
Log Server-Side Event
Tool to track server-side events in LeadBoxer. Use when tracking backend events, page views, or custom activities from your server. This endpoint supports tracking user interactions, conversions, and other activities that occur on the server-side.
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.
Get Custom Tracking Domains
Tool to fetch custom tracking domain entries for a dataset. Use when you need to retrieve all custom tracking domains that are created or in progress for a specific datasetId.
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.
Post Event Data
Tool to send event data for tracking user activities via POST request. Use when tracking events by sending data in the request body with application/x-www-form-urlencoded format.
Connect any two apps with Notis in the middle.
Notion and LeadBoxer, 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 LeadBoxer.