Channel Context to Jira User Data
Your team discusses who can do what in a Slack channel. This automation queries Jira's current user context to provide permission details, roles, and access info—perfect for understanding team capabilities mid-discussion.
Trigger
Channel Message Received
Triggered when a message is posted in a Slack channel (public, private, or multi-party IM). Does NOT match direct messages.
Action
Get Current User
Retrieves detailed information about the currently authenticated jira user.
Why this helps
Neurodivergent founders often need to understand who can do what in Jira but forget to check permissions and roles. Discussions stall while someone manually looks up user access levels.
- Provide permission context during Slack discussions without context-switching
- Build automations that respect Jira's role-based access
- Prevent miscommunication about who can assign, transition, or delete issues
- Create a record of permission checks for compliance or debugging
- Help new team members understand their Jira role instantly
Setup
Build it in a few focused steps.
- 1Connect Slack and Jira to Notis (one-time setup)
- 2Create an automation with this prompt: 'When a message is posted in the #permissions or #access-check channel, retrieve the current Jira user's role, permissions, and account details, then post a summary to the channel.'
- 3Select 'Channel Message Received' as your trigger and specify the channel
- 4Choose your Notis notification channel
- 5Test it: post 'Who am I?' or 'What can I do?' in the designated channel and watch Notis return your current user details and permissions
Questions about this workflow
Why would I use this instead of checking Jira directly?
This automation is useful for building downstream automations that need to understand user permissions programmatically. It's also helpful for team discussions about role clarity.
Does this expose sensitive permission info?
Yes, so use it in private channels or limit it to specific keywords. Notis will return details like your username, email, and permission scope.
Can I query another user's permissions?
No—Jira's API only exposes the current authenticated user's details. For compliance and security, you can't query arbitrary user permissions.
How do I use this in a workflow?
This action typically feeds data into other automations. For example, if the user has 'admin' permissions, trigger a different action than if they're a standard user.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Slack to Jira. A trigger fires from one place; an action lands in another.
Slack triggers
Jira actions
New Channel Created Trigger
Triggered when a new channel is created in Slack.
Add Attachment
Uploads and attaches a file to a jira issue.
Channel Message Received
Triggered when a message is posted in a Slack channel (public, private, or multi-party IM). Does NOT match direct messages.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
Direct Message Received
Triggered when a new direct message (DM) is sent to a user in Slack. Catches all DMs across all DM channels.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
Message Reaction Added
Triggered when a reaction is added to a message in Slack. Supports optional filtering by channel and emoji name.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Message Reaction Removed
Triggered when a reaction is removed from a message in Slack. Supports optional filtering by channel and emoji name.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Reaction Added Trigger
DEPRECATED: use `SLACK_MESSAGE_REACTION_ADDED` instead. Triggered when a reaction is added to a message in Slack.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
Reaction Removed Trigger
DEPRECATED: use `SLACK_MESSAGE_REACTION_REMOVED` instead. Triggered when a reaction is removed from a message.
Link Issues
Links two jira issues using a specified link type with optional comment.
New Bot Message Received Trigger
DEPRECATED: use `SLACK_CHANNEL_MESSAGE_RECEIVED` with `is_bot_message=true` instead. Triggered when a new bot message is posted to a Slack channel.
Create Project
Creates a new jira project with required lead, template, and type configuration.
Connect any two apps with Notis in the middle.
Not just Slack and Jira. Any combination from 985+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Jira.