Keep Jira absence coverage details current
When an absence plan changes, update the existing Jira issue with the latest HR-provided context and next step.
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
Coverage plans become unreliable when changes to an absence require someone to find and update the right ticket by hand.
- Keep the existing coverage issue current as HR details change.
- Reduce repeated coordination messages about outdated plans.
- Use a supplied issue identifier and update details.
Setup
Build it in a few focused steps.
- 1Connect Breathe HR and Jira once in the Notis portal.
- 2Create a new automation in Automations, then name it and add a prompt.
- 3Tell Notis to update the provided Jira coverage issue with the new absence details and explicitly supplied next steps.
- 4Choose a webhook trigger and select where run reports should go.
- 5Test with one real coverage change and the intended Jira issue.
Questions about this workflow
Will Notis find the right issue automatically?
The webhook or prompt should provide an issue key, or a reliable way to identify the correct issue. If the match is unclear, have Notis report the uncertainty.
Which Jira fields can it update?
The prompt can request an update to appropriate issue details supported by the Jira action, using information present in the webhook context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Breathe HR to Jira. A trigger fires from one place; an action lands in another.
Breathe HR 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.
Breathe HR 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.