Connect documentation changes to the right audience
A README update can change how people understand your product. Notis searches Onepage for relevant audience context so important follow-up does not disappear after the commit.
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
Search input post request
The searchinput endpoint allows users to perform a search query within the onepage platform. it accepts a required search string and optional parameters for language and output format customization. this endpoint is designed for retrieving relevant information based on user-specified search terms, with the ability to filter results by language and choose between structured (json) or plain text output. use this endpoint when you need to search for specific content or information within the onepage ecosystem. it's particularly useful for integrating search functionality into applications or workflows that interact with onepage data. note that this endpoint focuses solely on search functionality and does not provide additional features like content creation or modification.
Why this helps
Documentation work is shipped technically but its customer and partner impact is rarely reviewed.
- Make documentation updates more intentional
- Spot affected users and partners
- Reduce post-release follow-up gaps
Setup
Build it in a few focused steps.
- 1Connect GitHub and Onepage once in Notis.
- 2Create the automation through the portal or ask Notis to create it.
- 3Tell Notis: When the repository README changes, search Onepage for customers, partners, or companies who may care about the updated guidance and report the matches.
- 4Select the README-changed trigger, choose the run-report channel, and test with one documentation update.
Questions about this workflow
Can this watch a specific README location?
Yes. Configure the GitHub trigger for the relevant repository directory and branch.
Does it edit the README?
No. The workflow only searches Onepage.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Onepage. A trigger fires from one place; an action lands in another.
GitHub triggers
Onepage actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Search input post request
The searchinput endpoint allows users to perform a search query within the onepage platform. it accepts a required search string and optional parameters for language and output format customization. this endpoint is designed for retrieving relevant information based on user-specified search terms, with the ability to filter results by language and choose between structured (json) or plain text output. use this endpoint when you need to search for specific content or information within the onepage ecosystem. it's particularly useful for integrating search functionality into applications or workflows that interact with onepage data. note that this endpoint focuses solely on search functionality and does not provide additional features like content creation or modification.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Token details request
Retrieves detailed information about a specific token in the onepage system. this endpoint should be used when you need to obtain comprehensive data about a token, such as its associated permissions, expiration date, or other metadata. it's particularly useful for token management tasks, such as verifying token validity or checking token attributes. the endpoint accepts a single token and returns its corresponding details. it should not be used for token creation, deletion, or modification operations. note that the specific details returned may vary based on the onepage implementation and the token's type or purpose.
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.
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 Onepage, 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 Onepage.