Follow a release update with its published credential
When a release changes, close the recognition loop by sending its already-published credential to the intended recipient.
Trigger
GitHub Release State Changed
Triggers when a specific GitHub release (identified by tag name) changes. Monitors the release title, body/notes, draft flag, prerelease flag, published timestamp, target branch/commit, and the set of attached assets. The payload includes the full current release details, a list of which fields changed, and the previous values for comparison.
Action
Send a Credential
Tool to send a published credential via email. use after confirming the credential is published.
Why this helps
A credential can be ready in Certifier while the person who should receive it is still waiting for someone to send it.
- Turn release changes into a clear prompt for credential delivery.
- Send credentials that are already published in Certifier.
- Reduce manual follow-up after a release milestone.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Certifier once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, identify the published credential and recipient, and tell Notis to send only after confirming publication.
- 4Pick the GitHub Release State Changed trigger and choose where run reports go.
- 5Test with one real release change and confirm the credential is published.
Questions about this workflow
Does this workflow publish a credential?
No. It uses Certifier's Send a Credential action, which is for sending a credential after confirming it is published.
What should I include in the instruction?
Identify the credential and intended recipient, and tell Notis how to recognize the release change that should prompt delivery.
Can it send an unpublished credential?
No. Confirm that the credential is published before it is sent.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Certifier. A trigger fires from one place; an action lands in another.
GitHub triggers
Certifier actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Send a Credential
Tool to send a published credential via email. use after confirming the credential is published.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create, issue, and send credential
Tool to create, issue, and send a credential in a single request. use when group id and recipient details are ready.
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.
List Credential Interactions
Tool to list credential interactions. use when you need to retrieve interaction events for a specific credential, with optional filtering and pagination.
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.
List Credentials
Tool to list credentials. use after authentication to retrieve paginated credentials.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
List Designs
Tool to list all designs. use after authentication to retrieve certificate and badge designs with pagination.
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.
List Groups
Tool to list all groups. use when you need to retrieve groups with pagination (limit and cursor).
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 Certifier, 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 Certifier.