Turn Jira report requests into Digicert report updates
Keep scheduled report changes from getting lost between a Jira ticket and Digicert.
Trigger
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Action
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.
Why this helps
A report change request can require a separate follow-up in Digicert, leaving its status unclear in the original Jira issue.
- Starts from the Jira issue where the report change is requested.
- Can update an existing report's schedule, recipients, or format when the request provides the needed details.
- Returns a run report for easy follow-up.
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 update an existing Digicert report only when a Jira issue explicitly requests a report change and includes the required report and configuration details.
- 4Pick the Jira New Issue trigger and choose where run reports go.
- 5Test with one real report change request issue.
Questions about this workflow
Can this create a new Digicert report?
No. The available action updates an existing report's configuration.
What if the Jira issue does not identify the report or requested change?
Instruct Notis to flag the missing information in the run report rather than attempt an incomplete update.
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.