Keep campaign ownership aligned with project leads
A change in project lead can prompt Notis to refresh the related Hyperise prospect record, reducing follow-up confusion about who owns the campaign.
Trigger
Project Properties Updated
Fires when properties on a Linear project change (status, lead, target date, priority, etc.). 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
Ownership changes can be missed when the project and prospect record are maintained in different places.
- Keeps prospect ownership details aligned with project responsibility.
- Reduces ambiguity during campaign handoffs.
- Responds to an existing project properties update.
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.
- 3In one plain-language instruction, ask Notis to update the related Hyperise prospect record when a project lead changes.
- 4Choose Linear Project Properties Updated as the trigger and select a channel for run reports.
- 5Test with a real project lead change and inspect the related prospect record.
Questions about this workflow
Can the prospect be matched to a project?
Describe the relationship and identifying context in the instruction so Notis can apply it when the project properties change.
Does it handle other project changes?
The trigger can fire on project property changes; state that lead changes are the relevant case in the instruction.
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.