Skip to content
Notis

Browse Bible Books from a Notion Study Hub

Create a study subpage and get the book catalog at hand for choosing where to begin.

Trigger

Page Added to Page

Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.

Action

Get All Books

Tool to retrieve a list of all books in the bible. use when you need a catalog of every biblical book.

Why this helps

A broad study idea can be hard to turn into a concrete starting point.

  • Make the full book catalog available when a new study branch starts.
  • Turn an open-ended study plan into a more concrete next choice.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Api bible to Notis once in the portal.
  • 2Create an automation in the portal or tell Notis in plain language.
  • 3Use a single instruction asking Notis to retrieve all Bible books when a subpage is added under your Notion study hub.
  • 4Select the Page Added to Page trigger and choose a run-report channel.
  • 5Test by adding one study subpage under the intended parent page.

Questions about this workflow

When will it run?

It runs when a new subpage is added directly under the parent page selected for the trigger.

What will Api bible provide?

A catalog of all books in the Bible.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Notion to Api bible. A trigger fires from one place; an action lands in another.

Notion triggers

Api bible actions

Recurring trigger

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

TriggerScheduled

Get All Books

Tool to retrieve a list of all books in the bible. use when you need a catalog of every biblical book.

ActionInstant

Webhook trigger

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

TriggerInstant

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'.

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

Get Section

Tool to retrieve detailed content for a single section by id. use after listing sections.

ActionInstant

Comment Created

Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.

TriggerInstant

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.

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

Get Supported Bible Versions

Tool to retrieve supported bible versions. use when you need to list all available bible translations.

ActionInstant

Database Created

Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.

TriggerInstant

Search Verses

Tool to search for verses containing a specified query within a version.

ActionInstant

Data Source Created

Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.

TriggerInstant

Data Source Schema Updated

Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.

TriggerInstant

Connect any two apps with Notis in the middle.

Notion 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.