Get a regular view of your Hystruct webhook inventory
Choose a weekly time for Notis to retrieve your Hystruct webhook list and send you a compact review, so the check does not depend on remembering to do it.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Periodic configuration checks are easy to postpone when they rely on remembering to open Hystruct and inspect the account manually.
- Put a recurring webhook inventory check on a predictable schedule.
- Receive the account's current list without starting a separate manual lookup.
- Keep the result in the channel you already use for automation reports.
Setup
Build it in a few focused steps.
- 1Connect Notion and Hystruct to Notis once through the portal.
- 2In the portal, create an automation, or ask Notis conversationally to set up a weekly Hystruct webhook inventory.
- 3Write one plain-language instruction asking Notis to list the account's Hystruct webhooks and summarize the inventory on the chosen schedule.
- 4Select a recurring schedule and choose the channel for run reports.
- 5Run it once manually or wait for the first scheduled run, then review the inventory.
Questions about this workflow
Does the weekly check compare against a Notion document?
No. The available Hystruct action retrieves the current webhook list. The instruction can ask Notis to summarize that list for your review.
Can I choose when the check runs?
Yes. Choose a recurring schedule when creating the automation, such as weekly, and set the time that suits your routine.
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.