Turn ready resources into easy next steps
Mark a resource ready in Notion and let Notis keep the link in Linkhut.
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
Add bookmark
Adds a new bookmark to linkhut. the bookmark can be marked as private/public and read/unread, with optional tags and notes.
Why this helps
A resource marked for later can remain invisible until you remember where it lives.
- Make ready resources visible in your Linkhut library.
- Add the reason to revisit it.
- Avoid separate bookmarking after triage.
Setup
Build it in a few focused steps.
- 1Connect Notion and Linkhut once via the Notis portal.
- 2Create an automation in the portal or tell Notis what outcome to deliver.
- 3Write one instruction asking Notis to save a resource's URL when its Notion status becomes ready, including a short reminder note.
- 4Choose Page Properties Updated for the resource data source and select a run-report channel.
- 5Test by marking one real resource as ready.
Questions about this workflow
Can I use my own status wording?
Describe the status that means ready in the plain-language automation prompt.
What if the URL is missing?
Ask Notis to save a bookmark only when the record contains a usable URL.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Linkhut. A trigger fires from one place; an action lands in another.
Notion triggers
Linkhut actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add bookmark
Adds a new bookmark to linkhut. the bookmark can be marked as private/public and read/unread, with optional tags and notes.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete bookmark
This tool allows users to delete a bookmark from their linkhut account by providing the bookmark url. it operates independently and only requires the url parameter to identify and remove the bookmark.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get all tags
Retrieves a list of all tags and their usage counts for the authenticated user. no additional parameters required besides authentication.
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 bookmarks
This tool retrieves all bookmarks from the user's linkhut account. it makes a get request to the api endpoint and handles authentication. the tool returns a list of bookmarks including details such as url, title, tags, notes, and timestamp.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Update Bookmark
This tool allows users to update an existing bookmark in linkhut. the tool updates the metadata of a bookmark including its title, description, and tags.
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 Linkhut, 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 Linkhut.