Review connected Discord authorization as Jira grows
When a Jira project is added, have Notis retrieve the connected Discord authorization details so you can spot the app and scope context in one place.
Trigger
New Project
Triggered when a new project is added in Jira
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
As your Jira setup grows, remembering what the connected Discord authorization includes can add another manual check.
- Surface Discord app and scope details when a Jira project is added.
- Keep an integration review alongside the automation run.
- Reduce manual context switching during project setup.
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 the connected Discord OAuth2 authorization details when a project is added in Jira.
- 4Pick the Jira New Project trigger and choose where run reports go.
- 5Test with one real project event and review the returned authorization details.
Questions about this workflow
Will the action always include user details?
User data is contingent on the scopes granted, such as identify. The result reflects the current authorization.
Does this change Discord permissions?
No. The action retrieves current OAuth2 authorization details; it does not modify scopes or 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.