Issue contributor credentials after production deployments
Turn a shipped release into timely recognition without rebuilding the recipient list by hand.
Trigger
New Deployment Status Created
Triggers when a new deployment status is created for a specific deployment. Fires an event for each newly created deployment status on the monitored deployment. Deployment statuses represent state transitions such as pending, in_progress, success, failure, error, inactive, and queued. The payload includes the status state, creator, environment, description, timestamps, and relevant URLs.
Action
Bulk Create Credentials (V2)
Tool to bulk create credentials. use when batching up to 30 credentials in one call; supports multi-status (207) responses.
Why this helps
Release recognition is easy to intend and easy to postpone when a founder is already switching to the next urgent task.
- Recognize delivery while the achievement is fresh
- Keep release follow-up out of your mental queue
Setup
Build it in a few focused steps.
- 1Connect GitHub and Accredible certificates to Notis once.
- 2In the portal, create a new automation and name it Release recognition.
- 3Write one plain-language prompt telling Notis to issue credentials to qualifying contributors after a successful production deployment.
- 4Choose the GitHub deployment status trigger and a channel for run reports.
- 5Test it with one completed deployment.
Questions about this workflow
Can it limit recognition to production releases?
Yes. Describe production-only recognition in the prompt and choose the deployment status trigger.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Accredible certificates. A trigger fires from one place; an action lands in another.
GitHub triggers
Accredible certificates 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.
Bulk Create Credentials (V2)
Tool to bulk create credentials. use when batching up to 30 credentials in one call; supports multi-status (207) responses.
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.
Clone Group
Tool to clone an existing group. use after confirming the source group exists and you need a copy with optional overrides.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Create Collection
Tool to create a new collection. use when you need a curated set of groups.
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.
Create Evidence Item
Tool to create a new evidence item for a credential. use after confirming credential id.
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.
Create Group
Tool to create a new group. use after gathering all group details.
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.
Delete Credential
Tool to delete a credential. use after confirming you want to permanently remove an existing credential. executes delete on /credentials/{credential id} endpoint and returns status code.
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.
Delete Group
Tool to delete a group. use after confirming no credentials remain and when you need to permanently remove the group.
Commit Event
Triggered when a new commit is pushed to a repository.
Delete Reference
Tool to delete a specific reference by id. use after confirming both credential id and reference id. example: "delete reference 1234 from credential 'abc123'."
Connect any two apps with Notis in the middle.
Not just GitHub and Accredible certificates. 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 Accredible certificates.