Give each debugging investigation a Honeyhive session
Open an investigation page in Notion and let Notis start a Honeyhive session for the work.
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
Start Session
Tool to start a new session. Use when you need to initiate a new tracking session and retrieve its session_id.
Why this helps
Debugging notes and interaction tracking can begin at different times, making context harder to assemble.
- Create a tracking anchor as an investigation begins.
- Reduce setup overhead during debugging.
- Keep work notes connected to Honeyhive activity.
Setup
Build it in a few focused steps.
- 1Connect Notion and Honeyhive to Notis once through the portal.
- 2Create an automation to start a Honeyhive session for a new agent debugging page.
- 3Choose the Notion Page Created trigger for the debugging source and select a run report channel.
- 4Create one real debugging page and confirm a Honeyhive session is started.
Questions about this workflow
Will every new page start a session?
Scope the trigger to an appropriate parent page or data source and tell Notis which pages count as investigations.
What does the session provide?
The action starts a Honeyhive session and returns a session identifier for subsequent tracking.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Honeyhive. A trigger fires from one place; an action lands in another.
Notion triggers
Honeyhive actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add datapoints to dataset
Tool to add datapoints to a dataset. Use when you need to append multiple entries with specified input, ground truth, and history mappings.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Batch Model Events
Tool to create multiple model events in a single request. Use when you need to log a batch of event interactions to HoneyHive.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Batch Tool Events
Tool to log a batch of external API calls as tool events. Use when you need to record multiple tool events in one request—use after gathering all event data.
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.
Create Dataset
Tool to create a dataset. Use when you need to initialize a new dataset within a project.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Tool
Tool to create a new tool. Use when you need to register a new function or plugin for invocation.
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.
Delete Datapoint
Tool to delete a specific datapoint by its ID. Use when you need to remove a datapoint from HoneyHive after confirming its identifier.
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.
Delete Dataset
Tool to delete a dataset by ID. Use when you need to remove a dataset after confirming its ID.
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.
End Evaluation Run
Tool to mark an evaluation run as completed. Use after finishing manual evaluations to update the run status to completed.
Connect any two apps with Notis in the middle.
Notion and Honeyhive, 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 Honeyhive.