Review Bible translation options when a Jira project starts
Starting a Jira project for scripture related work? Get a list of Api bible's supported translations in the run report as a reference for planning.
Trigger
New Project
Triggered when a new project is added in Jira
Action
Get Supported Bible Versions
Tool to retrieve supported bible versions. use when you need to list all available bible translations.
Why this helps
Choosing a translation can stall early project planning when nobody has a ready list of supported options.
- Get the available translation list as soon as a project is added.
- Keep a translation reference with the automation's run report.
- Avoid a separate manual lookup while planning scripture related work.
Setup
Build it in a few focused steps.
- 1Connect Jira and Api bible once in the Notis portal.
- 2Create an automation and name it for your project planning process.
- 3In one instruction, ask Notis to retrieve Api bible's supported versions and include the list in the run report.
- 4Pick Jira's New Project trigger.
- 5Choose a report channel, then test with one real project event if available.
Questions about this workflow
Does this choose a translation for the project?
No. The action retrieves supported Bible versions. Use the report to review options, then decide which version your project should use.
Will it retrieve metadata for each version?
The supported versions action retrieves the available translations. The separate Get Bible by ID action can retrieve details for a specific version after you have its ID.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Api bible. A trigger fires from one place; an action lands in another.
Jira triggers
Api bible actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get All Books
Tool to retrieve a list of all books in the bible. use when you need a catalog of every biblical book.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Bible by ID
Tool to retrieve details of a specific bible version by its id. use when you need full metadata after listing versions. example prompt: 'get metadata for bibleid de4e12af7f28f599-01'.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Get Section
Tool to retrieve detailed content for a single section by id. use after listing sections.
New Project
Triggered when a new project is added in Jira
Get Sections
Tool to retrieve a list of sections for a specific book in a bible version. use after obtaining the bible and book ids to view sectional breakdown.
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.
Get Supported Bible Versions
Tool to retrieve supported bible versions. use when you need to list all available bible translations.
Search Verses
Tool to search for verses containing a specified query within a version.
Connect any two apps with Notis in the middle.
Jira and Api bible, 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 Api bible.