Refresh creator research when your positioning changes
A README edit often signals a sharper story. Let the audience report catch up automatically.
Trigger
GitHub Repository README Changed
Triggers when the README file in a specific repository directory changes. Monitors the README in a configurable directory and branch/tag/commit. The payload includes the current README metadata (filename, path, SHA, size, URLs), the previous and current git blob SHAs, and a list of which tracked fields changed.
Action
Get Instagram report
Tool to retrieve a detailed Instagram report. Use after providing username or user_id. Example: GET_REPORT_INSTAGRAM(username="nasa").
Why this helps
Positioning changes are documented in GitHub but creator research still reflects an older product narrative.
- Connects messaging updates to audience research
- Reduces stale campaign assumptions
- Supports clearer creator brief revisions
Setup
Build it in a few focused steps.
- 1Connect GitHub and HypeAuditor to Notis once through the portal.
- 2Create an automation telling Notis to generate an Instagram report when the monitored README changes.
- 3Select the GitHub README changed trigger and choose a run-report channel.
- 4Edit the README in a test branch and verify the report.
Questions about this workflow
Why use the README as a trigger?
For many products, README edits mark meaningful changes to positioning, onboarding, or audience messaging.
Can I monitor a specific branch?
Yes. Configure the README trigger for the repository location and branch that matter.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Hypeauditor. A trigger fires from one place; an action lands in another.
GitHub triggers
Hypeauditor actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Instagram Account Media
Tool to retrieve media content of an Instagram account. Use when you need detailed post-level data and performance metrics for analysis.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Instagram report
Tool to retrieve a detailed Instagram report. Use after providing username or user_id. Example: GET_REPORT_INSTAGRAM(username="nasa").
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.
Get TikTok Analytics Report
Tool to get TikTok analytics report. Use when fetching detailed performance metrics for a TikTok account.
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.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
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.
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.
Connect any two apps with Notis in the middle.
GitHub and Hypeauditor, 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 Hypeauditor.