Keep a Jira issue's scripture context current
As the question around a piece of work changes, send Notis the issue key and updated question. It can look up relevant passages and refresh the issue description with the new context.
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
An issue can keep outdated or incomplete context when the underlying question evolves and the research lives elsewhere.
- Keep the issue description aligned with the current question.
- Store updated passage references with the work they inform.
- Avoid manually revisiting and rewriting the issue after new research.
Setup
Build it in a few focused steps.
- 1Connect Api bible and Jira once in the Notis portal.
- 2Create an automation in Automations, New Automation, and provide its name and prompt.
- 3In one instruction, tell Notis to research the submitted question and update the specified Jira issue description with the question and relevant passage references.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one issue where updating the description is appropriate and review the result.
Questions about this workflow
What should the request include?
Include the Jira issue key and the updated scripture question.
Will this replace existing issue content?
The instruction should say how Notis should handle existing content. For example, ask it to preserve unrelated details and replace only the designated scripture context.
Can I control the translation?
Yes. Name the translation in the instruction or the request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Api bible to Jira. A trigger fires from one place; an action lands in another.
Api bible 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.
Api bible 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.