Refresh Translation Options When Study Plans Change
When a study page changes status or details, get the available translations in one step.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Get Supported Bible Versions
Tool to retrieve supported bible versions. use when you need to list all available bible translations.
Why this helps
A changed study plan can leave you unsure which reference materials are currently available.
- Surface translation choices after a study plan update.
- Keep planning and reference discovery in the same flow.
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 describe the desired outcome to Notis.
- 3Ask Notis in one instruction to retrieve supported Bible versions after a Notion study page's properties change.
- 4Choose the Page Properties Updated trigger and a channel for run reports.
- 5Test by updating a study page property.
Questions about this workflow
Which changes can trigger it?
The event fires when properties of a Notion page are updated; the prompt can describe the desired outcome.
Does this return Bible text?
No. The action lists supported Bible versions.
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.
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'.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Section
Tool to retrieve detailed content for a single section by id. use after listing sections.
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.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Supported Bible Versions
Tool to retrieve supported bible versions. use when you need to list all available bible translations.
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.
Search Verses
Tool to search for verses containing a specified query within a version.
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.
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.
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.