Move qualified prospects into relevant outreach
Update a prospect's status in Notion and let Notis prepare a Hyperise link that fits the next conversation.
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
Generate Personalized Short Link
Tool to generate a personalized short link. Use when you need a shareable URL with OGP metadata and per-recipient customizations. Provide image_hash and personalization data.
Why this helps
A status change can be easy to miss when preparing the next touch requires reopening the prospect record and building campaign material by hand.
- Turn a clear qualification update into a concrete next step.
- Avoid rebuilding prospect context when preparing outreach.
- Give the team a ready-to-share personalized destination.
Setup
Build it in a few focused steps.
- 1Connect Notion and Hyperise to Notis once through the portal.
- 2Create an automation by asking Notis to generate a Hyperise personalized short link when a Notion prospect is marked qualified.
- 3Pick the Notion Page Properties Updated trigger for the prospect data source and choose where run reports should arrive.
- 4Update one real prospect to qualified and check that the resulting link uses relevant details.
Questions about this workflow
Can the workflow react to a particular status?
Describe the qualified status in the plain-language instruction. The automation can inspect the Notion property update and act when it matches.
Does the link need a template?
Hyperise link generation uses an image template hash and personalization data. Ask Notis to use a suitable active template.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Hyperise. A trigger fires from one place; an action lands in another.
Notion triggers
Hyperise actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Client Account
Tool to create a new Hyperise client account. Use when an agency plan user needs to provision client sub-accounts.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Image Templates
Tool to list active image templates. Use when you need to retrieve all your current templates.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Generate Personalized Short Link
Tool to generate a personalized short link. Use when you need a shareable URL with OGP metadata and per-recipient customizations. Provide image_hash and personalization 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.
Hyperise Prospect Business Data (CRUD)
Tool to perform CRUD operations on Hyperise business prospect records. Use when managing business data via the Hyperise API.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
User Authentication
Tool to authenticate an API token and retrieve user details. Use after obtaining a valid API token from Hyperise settings.
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 Hyperise, 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 Hyperise.