Keep your documentation hub aware of README changes
Important product or setup changes surface where your team keeps its working documentation.
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
Create comment
Adds a comment by the user to a specific file, or as a reply to an other comment.
Why this helps
README updates can quietly change onboarding or product guidance without reaching the people who rely on Box documents.
- Improves documentation awareness
- Reduces silent process drift
- Creates a visible change trail
Setup
Build it in a few focused steps.
- 1Connect GitHub and Box to Notis once through the portal.
- 2Create an automation: “When the repository README changes, comment a summary on the related Box documentation item.”
- 3Select GitHub Repository README Changed as the trigger and choose a run-report channel.
- 4Test with a small README edit.
Questions about this workflow
Does it mirror the whole README?
No. The instruction can ask Notis to add a concise summary or link as a Box comment.
Is this useful for onboarding?
Yes. It surfaces setup and process changes where onboarding materials are stored.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Box. A trigger fires from one place; an action lands in another.
GitHub triggers
Box actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add classification to file
Adds a classification to a file by specifying the label of the classification to add. this api can also be called by including the enterprise id in the url explicitly, for example `/files/:id//enterprise 12345/securityclassification-6vmvochwuwo`.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add classification to folder
Adds a classification to a folder by specifying the label of the classification to add. this api can also be called by including the enterprise id in the url explicitly, for example `/folders/:id/enterprise 12345/securityclassification-6vmvochwuwo`.
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.
Add domain to list of allowed collaboration domains
Creates a new entry in the list of allowed domains to allow collaboration for.
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.
Add initial classifications
When an enterprise does not yet have any classifications, this api call initializes the classification template with an initial set of classifications. if an enterprise already has a classification, the template will already exist and instead an api call should be made to add additional classifications.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Add or update user avatar
Adds or updates a user avatar.
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.
Add shared link to file
Adds a shared link to a file.
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.
Add shared link to folder
Adds a shared link to a folder.
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.
Add shared link to web link
Adds a shared link to a web link.
Connect any two apps with Notis in the middle.
GitHub and Box, 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 Box.