Validate payment details from an intake request
If a custom intake flow already sends a Notis request, add an IBAN structure check without introducing another manual review step.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Payment details arriving through a connected intake process can sit unchecked while attention shifts to other work.
- Add validation to an existing intake handoff.
- Reduce manual structure checks for submitted IBANs.
- Keep a clear validation response within the Notis run.
Setup
Build it in a few focused steps.
- 1Connect Notion and Api labz to Notis once.
- 2Create the automation in the portal or ask Notis in plain language to validate the IBAN from an incoming request.
- 3Choose an incoming webhook trigger and a run-report channel; describe the validation outcome in one instruction.
- 4Send one real, authorized intake example to test the result.
Questions about this workflow
What sends the webhook?
An external tool or custom backend sends an HTTP request to start a Notis webhook workflow.
Does validation verify the payee?
The Api labz action validates IBAN structure; it does not verify account ownership.
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.