Keep destination maintenance connected to its request
Capture the decision in Notion, then have Notis update the named Hookdeck destination as requested.
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
Update Hookdeck Destination
Tool to update an existing Hookdeck destination. Use when you need to modify a destination's settings after creation.
Why this helps
Destination maintenance can be postponed when a request is easy to lose between a planning page and the configuration tool.
- Move an approved destination change into the existing operational workflow.
- Reduce repeated handoffs for routine endpoint maintenance.
- Keep run reporting alongside your Notion request.
Setup
Build it in a few focused steps.
- 1Connect Notion and Hookdeck to Notis once in the portal.
- 2Create an automation in Automations or ask Notis in plain language.
- 3Tell Notis in one instruction to update only the named Hookdeck destination after a reviewed Notion request clearly states the intended settings change.
- 4Select Page Properties Updated, choose a reporting channel, and test with one real approved maintenance request.
Questions about this workflow
Does the action create a new destination?
No. It updates an existing Hookdeck destination.
What should a request include?
Include enough context to identify the destination and clearly state the reviewed settings change.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Hookdeck. A trigger fires from one place; an action lands in another.
Notion triggers
Hookdeck actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Bulk Cancel Hookdeck Events
Tool to create a bulk cancellation job for events. Use when you need to cancel multiple events matching filters.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Bulk Retry Hookdeck Events
Tool to initiate a bulk retry for a set of events. Use when you need to retry multiple failed events matching filters.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Cancel Hookdeck Event
Tool to cancel all future delivery attempts for a specific event. Use when you need to stop retries of an event before manual intervention.
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.
Cancel Hookdeck Scheduled Retries
Tool to cancel all future scheduled retries for an event. Use when you need to mute automatic retry attempts after repeated failures.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Hookdeck Bookmark
Tool to create a new bookmark. Use when you want to bookmark a specific event for quick access.
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.
Create Hookdeck Connection
Tool to create a connection between a source and a destination. Use after setting up or referencing source/destination.
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.
Create Hookdeck Destination
Tool to create a new Hookdeck destination. Use after setting up sources when you need to route events to endpoints.
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.
Create Hookdeck Source
Tool to create a new Hookdeck source. Use after setting up your project when you need to receive and route incoming webhooks.
Connect any two apps with Notis in the middle.
Notion and Hookdeck, 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 Hookdeck.