Keep prospect follow-up details current
A project update about follow-up can prompt Notis to refresh the relevant Hyperise prospect record, giving the next touchpoint better context.
Trigger
Project Update Posted
Fires when a project status update is posted on the Linear project's Updates tab. Covers projects in both public and private teams — polls with the connected user's token.
Action
Hyperise Prospect Business Data (CRUD)
Tool to perform CRUD operations on Hyperise business prospect records. Use when managing business data via the Hyperise API.
Why this helps
Follow-up details can remain in a project update while the prospect record still reflects the old plan.
- Keeps follow-up context closer to the latest project update.
- Reduces manual copying after status communications.
- Makes the next outreach easier to prepare.
Setup
Build it in a few focused steps.
- 1Connect Linear and Hyperise to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Write one instruction asking Notis to update the matching Hyperise prospect record when a project update changes follow-up details.
- 4Choose Linear Project Update Posted as the trigger and select a channel for run reports.
- 5Test with one real project update and verify the prospect record reflects the follow-up change.
Questions about this workflow
What should the instruction include?
Describe which project updates contain a prospect follow-up change and what corresponding record information should be updated.
Can this help avoid dropped follow-ups?
It keeps the prospect record current when a relevant project update is posted, reducing reliance on manual copying.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Hyperise. A trigger fires from one place; an action lands in another.
Linear 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.
Comment Received Trigger
Triggered when a comment is received.
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.
Issue Created Trigger
Triggered when a new issue is created.
Hyperise Prospect Business Data (CRUD)
Tool to perform CRUD operations on Hyperise business prospect records. Use when managing business data via the Hyperise API.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
User Authentication
Tool to authenticate an API token and retrieve user details. Use after obtaining a valid API token from Hyperise settings.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear 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.