Answer Hystruct webhook questions with a current account check
When a teammate flags a Hystruct webhook question in Notion, get the current inventory in a Notis run report before replying.
Trigger
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.
Action
List All Webhooks
Tool to list all webhooks associated with the account. Use when you need to retrieve every configured webhook for your team.
Why this helps
A small configuration question can interrupt focused work while you open another tool and search for the relevant account details.
- Bring the current webhook list into the discussion workflow.
- Spend less time leaving the Notion thread to check account settings.
- Use an up-to-date inventory as a starting point for your reply.
Setup
Build it in a few focused steps.
- 1Connect Notion and Hystruct to Notis once through the portal; Notion comment access must be enabled for the connection.
- 2Create an automation in the portal or ask Notis conversationally to set one up.
- 3Give Notis one instruction: when a Notion comment asks about Hystruct webhooks, list the account's webhooks and summarize the result for the run report.
- 4Select the Comment Created trigger and choose where run reports should arrive.
- 5Add a test comment about a Hystruct webhook and review the report.
Questions about this workflow
Does the automation reply directly to the Notion comment?
No. The available Hystruct action retrieves the webhook list; Notis can report its result in the selected run-report channel.
What is needed for Notion comment events?
The Notion integration needs the Read comments capability. If it was authorized before that capability was enabled, re-authorize the connection.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Hystruct. A trigger fires from one place; an action lands in another.
Notion triggers
Hystruct actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List All Webhooks
Tool to list all webhooks associated with the account. Use when you need to retrieve every configured webhook for your team.
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 Hystruct, 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 Hystruct.