Check Digicert permissions from an updated Jira issue
Validate a required Digicert permission when a Jira ticket changes, and keep the result close to the work request.
Trigger
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
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
Teams may start a certificate operation before confirming that the authenticated Digicert user has the required permission.
- Uses an issue update to prompt a permission validation.
- Checks only the permission specified in an eligible Jira request.
- Makes the check outcome available in the run report channel.
Setup
Build it in a few focused steps.
- 1Connect Jira and Digicert once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, ask Notis to check a Digicert permission only when an updated Jira issue describes the intended operation and names the permission to validate.
- 4Pick the Jira Updated Issue trigger and choose where run reports go.
- 5Test with one real updated issue that names a permission to check.
Questions about this workflow
Does this grant the permission if the check fails?
No. The Digicert action checks whether a permission is available; it does not grant permissions.
Will comments trigger this workflow?
No. The Jira Updated Issue event does not fire on comment activity.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Digicert. A trigger fires from one place; an action lands in another.
Jira 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 Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
List API Access Roles
Tool to retrieve a list of available api access roles. use after confirming authentication with an api key.
New Project
Triggered when a new project is added in Jira
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.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
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.
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.
Connect any two apps with Notis in the middle.
Jira 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.