Skip to content
Notis

Automatically Sync Team Members in Jira

Your team roster is always current. Notis syncs Jira users on a schedule so you know who's active and available.

Trigger

Recurring schedule

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

Action

Get All Users

Retrieves all users from the jira instance including active, inactive, and other user states with pagination support.

Why this helps

Team membership in Jira drifts out of sync with reality. People who left are still listed, and new team members lack proper access or visibility.

  • Regular team roster updates
  • Clear visibility into active users
  • Catch deprovisioned accounts and inactive members
  • Ensure new team members are properly added
  • Reduce access control issues

Setup

Build it in a few focused steps.

  • 1Connect Notis and Jira.
  • 2Create a scheduled automation: 'Every [week/month], get all active users from Jira and report them to Slack or email.'
  • 3Notis retrieves the current roster and formats it as a report.
  • 4Review the report for any discrepancies (missing people, inactive accounts), then update Jira access as needed.

Questions about this workflow

Can I filter to specific projects or groups?

Yes. For example: 'Get all users in the Engineering project' or 'users with the Product Team label.'

What if someone should no longer have access?

Notis flags inactive accounts or people who left in the report. You can then deactivate them in Jira manually, or ask Notis to do it.

Can I see which projects each user can access?

Yes. The report can include per-user project permissions and role assignments.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Google Drive to Jira. A trigger fires from one place; an action lands in another.

Google Drive triggers

Jira actions

Comment Added (Docs/Sheets/Slides)

Triggers when a new comment is added to Google Docs, Sheets, or Slides.

TriggerPolling

Add Attachment

Uploads and attaches a file to a jira issue.

ActionInstant

File Created

Triggers when a new file is created in Google Drive.

TriggerPolling

Add Comment

Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.

ActionInstant

File Deleted or Trashed

Triggers when a file is moved to trash or permanently deleted in Drive.

TriggerPolling

Add Watcher to Issue

Adds a user to an issue's watcher list by account id.

ActionInstant

File Shared (Permissions Added)

Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.

TriggerPolling

Assign Issue

Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.

ActionInstant

File Updated

Triggers when a file's metadata or content changes in Google Drive.

TriggerPolling

Bulk Create Issues

Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.

ActionInstant

Google Drive Changes

Triggers when changes are detected in a Google Drive.

TriggerPolling

Create Issue

Creates a new jira issue (e.g., bug, task, story) in a specified project.

ActionInstant

New File Matching Query

Triggers when a new Google Drive file matches a provided query. This is the legacy query-centric trigger: it preserves Drive API query config such as ``corpora`` / ``driveId`` aliases and emits the historical ``file_matching_query`` event type. ``FileCreatedTrigger`` covers the broader "new file" case and emits ``file_created``.

TriggerPolling

Link Issues

Links two jira issues using a specified link type with optional comment.

ActionInstant

Create Project

Creates a new jira project with required lead, template, and type configuration.

ActionInstant

Connect any two apps with Notis in the middle.

Not just Google Drive and Jira. Any combination from 1,000+ 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.