Stop maintaining the same explanation twice
A README change should not leave your public tutorial quietly out of date.
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
Hashnode Update Comment
Tool to update an existing comment on a Hashnode post. Use after preparing updated content details.
Why this helps
Founders repeat documentation edits across GitHub and Hashnode and still miss one.
- Reduces duplicate documentation work
- Keeps onboarding guidance consistent
- Lowers maintenance overhead
Setup
Build it in a few focused steps.
- 1Connect GitHub and Hashnode to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it in plain language.
- 3Use this instruction: When the repository README changes, find the related Hashnode article and update its existing discussion with the latest setup or usage guidance.
- 4Select the README changed trigger, choose a reporting channel, and test with one meaningful README edit.
Questions about this workflow
Can it focus on one README path?
Yes. Configure the GitHub trigger for the relevant repository directory and branch.
Does it rewrite the entire article?
No. This workflow is designed to update an existing Hashnode comment with the changed guidance.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Hashnode. A trigger fires from one place; an action lands in another.
GitHub triggers
Hashnode actions
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.
Hashnode Accept Publication Invite
Tool to accept a publication invitation. Use when you have a valid invite token and want to join the publication.
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.
Hashnode Add Reply
Tool to add a reply to an existing comment. Use after confirming comment ID and reply content.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Hashnode: Check Custom Domain Availability
Tool to check if a custom domain is available for your Hashnode publication. Use when verifying domain mapping before setup.
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.
Hashnode: Fetch Invitations
Tool to fetch pending publication invitations. Use when you need to list current pending invites for a team-managed publication before taking further actions.
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.
Hashnode: Fetch Popular Tags
Tool to fetch a paginated list of popular tags. Use when you need to browse popular tags page by page.
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.
Fetch Publication Posts
Tool to fetch a paginated list of posts from a publication. Use when you need to list posts page by page for a given publication host.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Fetch Series Posts
Tool to fetch posts from a series within a publication. Use when retrieving and paginating through series posts in a specific publication.
Commit Event
Triggered when a new commit is pushed to a repository.
Fetch Single Article
Tool to fetch a single article by slug from a publication. Use when you need the detailed content of a specific post.
Connect any two apps with Notis in the middle.
Not just GitHub and Hashnode. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Hashnode.