Keep documentation changes understandable
Know who a documentation update is written for before it creates confusion downstream.
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
Identify Language
This tool identifies the natural language of a given text. it takes a string of text as input and returns the detected language along with a confidence score. optional parameters include specifying a genre (e.g., "social-media"), providing a list of language codes to constrain the identification, and indicating whether to include user-defined languages.
Why this helps
README changes can quietly affect onboarding, support, and contributors before anyone notices a language mismatch.
- Adds visibility to documentation audience changes.
- Helps catch language mismatches earlier.
- Supports smoother contributor and customer onboarding.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Rosette text analytics to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it with a plain-language request.
- 3Use this instruction: Identify the language of changed README content and report the repository, path, detected language, confidence, and README link.
- 4Pick the GitHub Repository README Changed trigger and choose a reporting channel.
- 5Test it with one README update.
Questions about this workflow
Can this monitor a README in a specific directory?
Yes. The GitHub trigger supports a configurable repository directory.
Will Notis rewrite the README?
No. It reports language context only.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Rosette text analytics. A trigger fires from one place; an action lands in another.
GitHub triggers
Rosette text analytics actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Address Similarity
Compares two addresses and returns a similarity score. addresses can be provided as single strings or as structured objects. the tool is optimized for english, simplified chinese, and traditional chinese addresses.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Identify Language
This tool identifies the natural language of a given text. it takes a string of text as input and returns the detected language along with a confidence score. optional parameters include specifying a genre (e.g., "social-media"), providing a list of language codes to constrain the identification, and indicating whether to include user-defined languages.
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.
Compare Name Similarity
The 'name similarity' tool compares two entity names (person, location, or organization) and returns a similarity score between 0 and 1 to indicate if the names are similar. it is useful for tasks such as record linkage, identity resolution, and data deduplication.
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 Rosette text analytics, 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 Rosette text analytics.