Verify credentials when Jira work changes
Turn an issue update into a focused verification check and a clear run report.
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
Verify Credential or Presentation
Tool to verify a verifiable credential or presentation. Use after receiving a credential or presentation from an issuer.
Why this helps
Verification can slip when ticket changes are handled separately from credential checks.
- Run a verification check in response to a relevant issue update.
- Keep the verification outcome close to the work that prompted it.
- Reduce missed checks caused by switching between tools.
Setup
Build it in a few focused steps.
- 1Connect Jira and Dock certs once in the Notis portal.
- 2Create an automation in Automations, New Automation, and provide a name and prompt.
- 3In one instruction, ask Notis to verify the credential or presentation supplied with the relevant issue context and summarize the result.
- 4Pick the Jira Updated Issue trigger and choose where run reports should go.
- 5Test with one real issue update and a credential or presentation available to the automation.
Questions about this workflow
Does Jira provide the credential or presentation automatically?
The listed Jira trigger only guarantees an issue update. Supply the credential or presentation in the information available to the automation; do not assume the trigger includes it.
Do comment changes trigger this workflow?
No. The Updated Issue trigger does not fire on comment activity.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Dock certs. A trigger fires from one place; an action lands in another.
Jira triggers
Dock certs actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create API Key
Tool to create an API key. Use when you need to generate a new API key with optional alias and IP allowlist.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Webhook
Tool to create a webhook endpoint. Use when you need Dock.io to push event notifications to your service.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Delete API Key
Tool to delete a specific API key. Use after confirming the API key's ID via list_api_keys.
New Project
Triggered when a new project is added in Jira
Delete Credential
Tool to delete a verifiable credential. Use after confirming the credential is no longer needed.
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.
Delete Tag
Tool to delete a specific tag. Use when you have a tag ID and want to permanently remove it.
Delete Webhook
Tool to delete a specific webhook. Use after confirming the webhook's ID via list_webhooks.
Retrieve API Key
Tool to retrieve details of an API key. Tries single-key endpoint first, then falls back to listing and filtering.
Retrieve API Keys
Tool to list all API keys. Use when you need to retrieve all API keys for the authenticated account.
Connect any two apps with Notis in the middle.
Jira and Dock certs, 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 Dock certs.