See Discord server access when Jira work begins
A new issue can prompt a quick check of the Discord servers available to your connected account, with the result delivered where you track automation runs.
Trigger
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Action
List my guilds
Lists the current user's guilds, returning partial data for each; primarily used for displaying server lists or verifying memberships.
Why this helps
New work can start before you know whether the connected Discord account has access to the server where coordination happens.
- Check available Discord guilds when a Jira issue appears.
- Keep the result with your Notis run reports.
- Avoid switching apps for a basic access check.
Setup
Build it in a few focused steps.
- 1Connect Jira and Discord once in the Notis portal.
- 2Create an automation and give it a clear name.
- 3Tell Notis to list the connected Discord account's guilds when a Jira issue is created.
- 4Pick the Jira New Issue trigger and choose where run reports go.
- 5Test with one real issue and review the reported guild list.
Questions about this workflow
Does this check whether a particular teammate is in a Discord server?
No. The available action lists guilds for the currently authenticated Discord account; it does not look up another user's membership.
Can I limit the Jira trigger to certain issues?
The New Issue event fires for issues in the configured Jira project. The user does not build filters during setup.
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.