Share README updates with sensitive text concealed
Documentation updates may expose internal details. Let Notis anonymize selected strings when a monitored README changes.
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
Anonymize Value
Tool to anonymize a string or array of string values. use when you need to conceal sensitive text before storage or transmission. example: `anonymizevalue().execute(anonymizevaluerequest(data=['secret']))` limitations: only supports list of strings, not nested structures.
Why this helps
Turning documentation edits into team updates can require careful manual redaction each time.
- Reduce manual redaction in documentation update notes.
- Make change context easier to share across the team.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Anonyflow once in the Notis portal.
- 2Create a Notis automation and describe the outcome in plain language.
- 3In one instruction, ask Notis to summarize the README change and anonymize sensitive string values with Anonyflow.
- 4Pick the README changed trigger and choose where run reports go.
- 5Test with one real README change.
Questions about this workflow
Can the trigger monitor a specific README location?
Yes. The event monitors a README in a configurable directory and branch, tag, or commit.
Will Anonyflow accept the whole README content structure?
Anonymize Value accepts lists of strings, not nested structures. Ask Notis to identify relevant strings from the change.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Anonyflow. A trigger fires from one place; an action lands in another.
GitHub triggers
Anonyflow actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Anonymize Value
Tool to anonymize a string or array of string values. use when you need to conceal sensitive text before storage or transmission. example: `anonymizevalue().execute(anonymizevaluerequest(data=['secret']))` limitations: only supports list of strings, not nested structures.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Deanonymize Packet
Tool to deanonymize a json data packet using your private key. use after receiving an anonymized packet to recover specific fields.
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.
Deanonymize Value
Tool to deanonymize one or more anonymized string values. use when you need to recover the original plaintext values after encryption-based anonymization. example: `deanonymizevalue().execute(deanonymizevaluerequest(data=["<anonymized string>"]))`
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.
Test Connection
Tool to test the connection to the anonyflow api. use when verifying that the anonyflow service is reachable and operational before performing anonymization tasks. example: `testconnection().execute(testconnectionrequest())`
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 Anonyflow, 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 Anonyflow.