Keep Discord authorization context current with Jira changes
When an existing Jira issue changes, Notis can refresh the connected Discord authorization details for quick review.
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 my OAuth2 authorization
Retrieves current oauth2 authorization details for the application, including app info, scopes, token expiration, and user data (contingent on scopes like 'identify').
Why this helps
Authorization context can be forgotten as work evolves and the connected account or scopes change over time.
- Refresh authorization details on issue changes.
- Review available scopes in the run report.
- Keep integration context close to active work.
Setup
Build it in a few focused steps.
- 1Connect Jira and Discord once in the Notis portal.
- 2Create an automation and name it for the authorization review.
- 3Tell Notis to retrieve current Discord OAuth2 authorization details when a Jira issue is updated.
- 4Pick the Jira Updated Issue trigger and choose where run reports go.
- 5Test with one real issue update and review the returned details.
Questions about this workflow
Does the trigger include comments?
No. Jira's Updated Issue trigger does not fire on adding, editing, or deleting comments.
Can the workflow grant new Discord scopes?
No. It retrieves the existing OAuth2 authorization information and does not change permissions.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Discord. A trigger fires from one place; an action lands in another.
Jira triggers
Discord actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Invite
Tool to retrieve information about a specific invite code. use when you need to get details about a guild or channel associated with an invite.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get my guild member
Retrieves the guild member object for the currently authenticated user within a specified guild, provided they are a member of that guild.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Get my OAuth2 authorization
Retrieves current oauth2 authorization details for the application, including app info, scopes, token expiration, and user data (contingent on scopes like 'identify').
New Project
Triggered when a new project is added in Jira
Get my user
Fetches comprehensive profile information for the currently authenticated discord user, including email if the 'email' scope is granted.
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.
Retrieve user connections
Retrieves a list of the authenticated user's connected third-party accounts on discord.
List my guilds
Lists the current user's guilds, returning partial data for each; primarily used for displaying server lists or verifying memberships.
Connect any two apps with Notis in the middle.
Jira and Discord, 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 Discord.