Connect Jira to Async interview

When something happens in Jira, Notis takes the next step in Async interview. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Jira to Async interview

View example

Show interview jobs when a hiring ticket opens

When a Jira issue requests hiring work, retrieve Async interview jobs and send a concise inventory to your report channel.

View example

Reflect Jira role changes in an interview job

When an existing Jira issue changes, have Notis assess whether it calls for an interview job detail update and apply the requested change.

View example

Review interview jobs after a Jira status change

When an issue changes, retrieve the Async interview job list for a status review and report jobs that appear relevant to the issue.

View example

Check interview jobs when a Jira project is added

When a Jira project is created, list Async interview jobs and share an inventory to help orient a new project owner.

View example

Refresh interview job details from a changed requirement

When a Jira issue changes, apply a clearly requested requirement adjustment to the existing related Async interview job.

View example

Update an interview job when a Jira issue requests a pause

When a Jira issue changes, have Notis apply a clearly requested pause or other supported detail change to the related interview job.

View example

Apply a new Jira role brief to an interview job

When a new role-related Jira issue is created, update a clearly identified existing Async interview job with the requested details.

View example

Review open interview jobs for a new hiring issue

When a new hiring issue arrives, list Async interview jobs and report likely related work for a quick human check.

View example

Refresh an interview job when a Jira project starts

On Jira project creation, update a related existing interview job only when project details clearly specify a change.

Supported Triggers and Actions

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

Jira triggers

Async interview actions

Recurring trigger

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

TriggerScheduled

Delete Job

Tool to delete an interview job. use when you need to permanently remove a job after reviewing responses.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

List Jobs

Tool to retrieve a list of all interview jobs. use when you need to display or manage existing jobs.

ActionInstant

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Update Job

Tool to update an existing interview job. use when you need to modify job details after creation.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

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.

TriggerInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.