Validate Contractor IBANs on Onboarding
Neurodivergent founders do not have bandwidth for contractor payment chaos. Validate IBANs automatically when hiring to avoid delays.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Validate IBAN
Tool to validate the format and country code of an iban number. use after collecting an iban to ensure it is correctly formatted.
Why this helps
Failed contractor payments delay work and damage contractor relationships before collaboration even starts.
- Ensure contractors get paid on first attempt with verified banking info
- Smooth contractor onboarding without payment delays
- Reduce back-and-forth corrections on banking details
Setup
Build it in a few focused steps.
- 1Connect your Notion contractor database and Abstract account to Notis.
- 2Tell Notis: 'When I add a new contractor and their IBAN, validate that IBAN format immediately.'
- 3Set trigger to 'New Page in Database' on your contractors table.
- 4Select your notification channel for validation alerts.
- 5Add a test contractor with an IBAN to verify the validation workflow.
Questions about this workflow
What if a contractor's IBAN fails validation?
Notis will flag the issue in Notion so you can ask the contractor to double-check and resubmit their correct banking details.
Can I set up automated payment once IBAN is validated?
Yes--you can create a follow-up automation that queues the contractor for payment processing once IBAN validation passes.
Does this work for contractors outside the EU?
This workflow focuses on IBAN validation, which is used in EU and select other countries; for non-IBAN countries, you would use different payment methods.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Abstract. A trigger fires from one place; an action lands in another.
Notion triggers
Abstract actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Validate IBAN
Tool to validate the format and country code of an iban number. use after collecting an iban to ensure it is correctly formatted.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Email reputation
Tool to enrich an email address with reputation and risk scoring data. use when you need to assess an address's deliverability and risk before outreach. use after confirming your api key is valid.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Email Validation
Tool to validate whether an email address is real and deliverable. use after collecting an email address to confirm deliverability.
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.
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 Abstract, 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 Abstract.