Give readers a clearer signal when work is ready
Readiness is easier to trust when the testing story is visible.
Trigger
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.
Action
Hashnode Add Comment
Tool to add a comment to a Hashnode post. Use after obtaining story ID and content, optionally provide a parent comment ID for replies.
Why this helps
The founder knows whether a change is ready, but readers only see silence or outdated content.
- Makes readiness more transparent
- Connects testing with communication
- Reduces uncertainty around launches
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 conversationally.
- 3Use this instruction: When the GitHub check suite changes conclusion for the release ref, add a concise update to the related Hashnode discussion describing the reader-facing readiness signal.
- 4Choose the check suite trigger, select a reporting channel, and test with one completed suite.
Questions about this workflow
Can it cover multiple checks in a suite?
Yes. The trigger monitors the suite conclusion and Notis can summarize the overall result.
Does it publish release notes?
No. It adds an update to an existing Hashnode discussion.
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
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Hashnode Accept Publication Invite
Tool to accept a publication invitation. Use when you have a valid invite token and want to join the publication.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Hashnode Add Reply
Tool to add a reply to an existing comment. Use after confirming comment ID and reply content.
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: Check Custom Domain Availability
Tool to check if a custom domain is available for your Hashnode publication. Use when verifying domain mapping before setup.
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: 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.
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: Fetch Popular Tags
Tool to fetch a paginated list of popular tags. Use when you need to browse popular tags page by page.
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.
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.
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.
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.
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 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.
GitHub and Hashnode, 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 Hashnode.