Connect Breezy Hr to Jira

When something happens in Breezy Hr, Notis takes the next step in Jira. 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 Breezy Hr to Jira

View example

Turn applicant submissions into Jira intake issues

Create a Jira issue when an applicant submission arrives through a Notis webhook, so recruiting follow-up has a clear home.

View example

Create a Jira triage batch for open candidates

On a recurring schedule, review open recruiting candidates and create a Jira issue for each candidate needing team attention.

View example

Add interview feedback to the recruiting Jira issue

When a webhook carries interview feedback, add a readable comment to the related Jira issue to keep the decision context together.

View example

Refresh Jira follow-up for candidates needing attention

Review recruiting data on a schedule and update existing Jira issues when candidate follow-up needs a fresh status or context.

View example

Assign recruiting follow-up to the right Jira owner

Use applicant or recruiting handoff details in a webhook to assign the related Jira issue to the named owner.

View example

Review Jira recruiting work against the open candidate queue

On a schedule, search Jira for recruiting follow-up issues and compare them with the open candidate queue to surface work needing attention.

View example

Notify the team about urgent recruiting blockers

Send a Jira notification when webhook details indicate a recruiting blocker needs prompt team attention.

View example

Refresh Jira recruiting comments with current candidate context

On a schedule, revise a specified Jira comment with updated candidate context when the recruiting data has changed.

View example

Link Jira issues for related hiring work

When recruiting information arrives by webhook, link the Jira issues involved in the same hiring effort so the team can navigate related work.

Supported Triggers and Actions

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

Breezy Hr triggers

Jira actions

Recurring trigger

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

TriggerScheduled

Add Attachment

Uploads and attaches a file to a jira issue.

ActionInstant

Webhook trigger

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

TriggerInstant

Add Comment

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

ActionInstant

Add Watcher to Issue

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

ActionInstant

Assign Issue

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

ActionInstant

Bulk Create Issues

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

ActionInstant

Create Issue

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

ActionInstant

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

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.