Check revised bank details before payment
A changed payment detail should prompt a fresh check, so an edit does not quietly pass through the workflow unnoticed.
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
Validate IBAN
Tool to validate international bank account numbers (ibans). use when you need to verify an iban's structure before processing transactions.
Why this helps
Updated bank details can be missed when the team assumes an earlier validation still applies.
- Revisit the IBAN after a relevant property change.
- Reduce reliance on memory to repeat a check.
- Keep payment review steps linked to the updated Notion item.
Setup
Build it in a few focused steps.
- 1Connect Notion and Api labz to Notis once.
- 2Create an automation through the portal or by asking Notis for the outcome in plain language.
- 3Ask Notis in one instruction to validate the IBAN after payment details change; select Page Properties Updated and a run-report channel.
- 4Test by editing a real payment entry and reviewing the Api labz validation.
Questions about this workflow
Should every property update trigger a check?
Use the prompt to describe the payment-detail change that matters, and select the relevant Notion data source if appropriate.
What does the Api labz action return?
It validates IBAN structure, which can help identify formatting or checksum problems.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Api labz. A trigger fires from one place; an action lands in another.
Notion triggers
Api labz actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Validate IBAN
Tool to validate international bank account numbers (ibans). use when you need to verify an iban's structure before processing transactions.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Integrate Deal
Tool to integrate a deal into api labz. use when you need to push a new or updated deal record into the system after preparing required fields.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Airtable Tables
Tool to list all airtable tables for a given base. use when you need to retrieve table names before interacting with a table.
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.
Trello AI Search Engine
Tool to search trello boards, lists, and cards using ai-driven queries. use when you need to quickly locate relevant trello cards, lists, or boards.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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 labz, 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 labz.