Keep the connected Discord profile easy to verify
A change to an existing Jira issue can prompt Notis to fetch the authenticated Discord user's profile and place the result in your 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
Get my user
Fetches comprehensive profile information for the currently authenticated discord user, including email if the 'email' scope is granted.
Why this helps
It is easy to lose track of which Discord account is connected while work moves between tools.
- Retrieve connected-account profile context when an issue changes.
- Review the result without opening another app.
- Keep the workflow grounded in the authenticated Discord account.
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 profile check.
- 3Tell Notis to retrieve the connected Discord user's profile 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 profile returned.
Questions about this workflow
Can it fetch any Discord user's profile?
No. This action fetches the profile of the currently authenticated Discord user, including email only if the email scope is granted.
Do Jira comment changes start this workflow?
No. The Jira 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 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.