Bring authorization details into Jira review follow-up
When a review issue changes, fetch the referenced authorization request details for a more informed follow-up.
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
Get Authorization Request
Tool to fetch details of a specific authorization request. Use when you need to retrieve metadata by authorization_request_id.
Why this helps
Reviewers lose time switching tools to check the status and details of a referenced authorization request.
- Retrieve details for a specific authorization request referenced in an updated issue.
- Put the returned context in the Notis run report.
- Avoid treating a Jira comment as the trigger, since comment activity does not fire this event.
Setup
Build it in a few focused steps.
- 1Connect Jira and Conveyor once in the Notis portal.
- 2Create an automation by telling Notis the outcome you want, in the portal or from any channel.
- 3In one instruction, ask Notis to retrieve details for the Conveyor authorization request ID stated in the updated Jira issue and include the result in the run report.
- 4Pick the Jira Updated Issue trigger and choose where run reports should go.
- 5Test with one real issue that includes a valid authorization request ID.
Questions about this workflow
Does a comment edit trigger this workflow?
No. Jira Updated Issue fires when an issue is changed, but the listed event does not fire on comment activity.
What if the issue has no authorization request ID?
Notis needs an authorization_request_id to fetch a specific request. Ask it to report that the ID is missing and skip the lookup.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Conveyor. A trigger fires from one place; an action lands in another.
Jira triggers
Conveyor actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete a Conveyor document
Tool to delete a specific document. Use when you need to remove a document by its ID.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete folder
Tool to delete a folder by its ID. Use when you need to remove a specific folder after confirming its ID.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Generate/Validate API Token Guidance
Tool to validate API token and provide guidance. Conveyor does not support API-based token creation; tokens must be created in the Conveyor UI. This action performs a real API call (using the provided metadata) to validate the existing API token and returns structured guidance.
New Project
Triggered when a new project is added in Jira
Get Authorization Request
Tool to fetch details of a specific authorization request. Use when you need to retrieve metadata by authorization_request_id.
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.
Get Authorization Requests
Tool to fetch authorization requests. Use when you need to list authorization requests, optionally filtered by status.
Get all authorization requests
Tool to retrieve all authorization requests. Use when you need to list all authorizations; optionally filter by status. Use after authenticating with a valid API token.
Get all Conveyor connections
Tool to retrieve all connections. Use when you need to fetch the complete list of your Conveyor connections. Use after authenticating with a valid API key.
Get all Conveyor documents
Tool to retrieve all documents. Use after authenticating with a valid API key.
Connect any two apps with Notis in the middle.
Jira and Conveyor, 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 Conveyor.