Check Digicert access when a new GitHub issue arrives
Issues can capture work that needs action in another system. Have Notis check the Digicert permission you specify and report whether the authenticated user can perform that operation.
Trigger
New Issue Created
Triggers when a new issue is created in a GitHub repository. Pull requests are automatically excluded -- only true issues produce events. Results can be filtered by labels, assignee, creator, and mentioned user. The payload includes the issue number, title, body, state, labels, assignees, comment count, creator details, timestamps, and direct links to the issue on GitHub.
Action
Check Permission
Tool to check if a specific permission is available. use when validating that the authenticated user may perform an operation before attempting it.
Why this helps
An issue may call for a cross-tool task, but confirming access adds another step before the work can move forward.
- Check a specified Digicert permission when a new issue arrives.
- Make access readiness visible in a Notis run report.
- Reduce manual lookup during issue triage.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Digicert once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis what to do from any channel.
- 3In one instruction, specify the Digicert permission to check and ask Notis to report the result for triage.
- 4Pick New Issue Created as the trigger.
- 5Choose where run reports go, then test with one real issue.
Questions about this workflow
Can Notis check every permission implied by an issue?
Name the specific permission to check in your instruction. The available action checks a specific permission.
Will this workflow perform the operation after checking access?
No. It checks whether a permission is available and reports the result; it does not perform the operation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Digicert. A trigger fires from one place; an action lands in another.
GitHub triggers
Digicert actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Permission
Tool to check if a specific permission is available. use when validating that the authenticated user may perform an operation before attempting it.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create API Key
Tool to create a new api key with specified permissions. use when you have a valid digicert user id and need to generate a new key. note the api key appears only once; save it securely.
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 API Access Roles
Tool to retrieve a list of available api access roles. use after confirming authentication with an api key.
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 Intermediate Certificates
Tool to retrieve a list of intermediate certificates. use when you need to list all intermediate certificates for your account. no input required.
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 CertCentral Users
Tool to retrieve a list of certcentral account users. use when you need to audit or manage users with support for pagination and optional detail inclusion.
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.
Update Report
Tool to update an existing report’s configuration. use when you need to modify the schedule, recipients, or format of a scheduled report.
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 Digicert, 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 Digicert.