Keep Jira current when member details change
Route meaningful profile changes into the Jira work already tracking the member or request.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Edit Issue
Updates an existing jira issue with field values and operations. supports direct field parameters (summary, description, assignee, priority, etc.) that are merged with the fields parameter. direct parameters take precedence.
Why this helps
A changed member detail may leave an existing Jira task stale, causing teammates to act on old information.
- Add current profile context to an existing Jira issue.
- Reduce duplicate issues when the work already has a tracking ticket.
- Keep the next step visible to the teammate handling it.
Setup
Build it in a few focused steps.
- 1Connect Brilliant Directories and Jira once in the Notis portal.
- 2Create an automation in the portal or by telling Notis what it should do.
- 3In one instruction, explain which profile changes matter and how to find the related Jira issue to update.
- 4Choose a webhook trigger and a run report destination.
- 5Test with one real profile change and confirm the intended Jira issue was updated.
Questions about this workflow
How does Notis identify the Jira issue to update?
Describe a reliable lookup method in the prompt, such as an issue key included in the event or a Jira search using available member context. If there is no reliable match, have the instruction report that instead of guessing.
Will every profile change cause an update?
Not necessarily. Tell Notis which changes warrant action. The automation can inspect returned data, but criteria or history not supplied by Brilliant Directories must be specified.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Brilliant directories to Jira. A trigger fires from one place; an action lands in another.
Brilliant directories triggers
Jira actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Attachment
Uploads and attaches a file to a jira issue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
Link Issues
Links two jira issues using a specified link type with optional comment.
Create Project
Creates a new jira project with required lead, template, and type configuration.
Connect any two apps with Notis in the middle.
Brilliant directories and Jira, 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 Jira.