Turn repository interest into organized follow-up
A new star is a signal of interest. Preserve it before it disappears in the activity stream.
Trigger
New Stargazer Added
Triggers when a new user stars a GitHub repository. Emits an event for each new stargazer detected on the monitored repository.
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
Early interest arrives asynchronously, and founders may notice it too late to connect it with a relevant conversation.
- Captures an interest signal automatically
- Creates a place for future personalization
- Reduces manual monitoring of repository activity
Setup
Build it in a few focused steps.
- 1Connect GitHub and Hyperise to Notis once in the portal.
- 2Create the automation in the portal or ask Notis to add each new stargazer as a Hyperise prospect record.
- 3Pick the New Stargazer Added trigger and describe any criteria for meaningful follow-up.
- 4Choose a reporting channel and test with one new star.
Questions about this workflow
Is this suitable for open source projects?
Yes. It helps founders organize interest from users, contributors, and potential customers.
Does it send outreach automatically?
No. It creates the Hyperise prospect record so outreach can be considered with context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Hyperise. A trigger fires from one place; an action lands in another.
GitHub triggers
Hyperise actions
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Create Client Account
Tool to create a new Hyperise client account. Use when an agency plan user needs to provision client sub-accounts.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
List Image Templates
Tool to list active image templates. Use when you need to retrieve all your current templates.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Hyperise Prospect Business Data (CRUD)
Tool to perform CRUD operations on Hyperise business prospect records. Use when managing business data via the Hyperise API.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
User Authentication
Tool to authenticate an API token and retrieve user details. Use after obtaining a valid API token from Hyperise settings.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Commit Event
Triggered when a new commit is pushed to a repository.
Connect any two apps with Notis in the middle.
Not just GitHub and Hyperise. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Hyperise.