Look up BIN details after a Notion record update
Get context for a card BIN prefix as part of reviewing the record, without starting a separate lookup task.
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
BIN Lookup
Tool to perform a bin (bank iin) lookup. use when you need card details for a bin prefix.
Why this helps
A bare BIN prefix in a record may need context before it can be reviewed or triaged.
- Retrieve card details associated with a BIN prefix.
- Keep a lookup connected to the record being reviewed.
- Reduce manual research for a narrowly defined payment-data task.
Setup
Build it in a few focused steps.
- 1Connect Notion and Neutrino to Notis once in the portal.
- 2Create an automation in the portal, or ask Notis to look up BIN details when a relevant record changes.
- 3Use one plain-language instruction to identify the BIN prefix and report the returned card details.
- 4Choose Page Properties Updated for the relevant data source and select a run-report channel.
- 5Test with one real record containing a BIN prefix.
Questions about this workflow
What does BIN Lookup need?
It performs a lookup using a bank identification number prefix.
Is this useful for every finance record?
It is appropriate only when the record contains a BIN prefix that needs card details.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Neutrino. A trigger fires from one place; an action lands in another.
Notion triggers
Neutrino actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Bad Word Filter
Tool to detect bad words and profanity in text. use when scanning content for swear words.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
BIN Lookup
Tool to perform a bin (bank iin) lookup. use when you need card details for a bin prefix.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Convert Value
Tool to perform unit and currency conversions. use when you need to convert a value from one unit or currency to another. example: convert 100 usd to eur.
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.
Validate and analyze an email address
Tool to parse, validate, and clean an email address. use after gathering the email to ensure deliverability and correct typos.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Verify Email Address
Tool to verify and analyze the deliverability of an email address. use when you need smtp-based validation before sending emails.
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.
Geocode Address
Tool to geocode an address. use when you need geographic coordinates for an address or place name.
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.
Reverse Geocode
Tool to convert geographic coordinates to a physical address. use when you have latitude and longitude and need a real-world address.
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.
HLR Lookup
Tool to perform real-time hlr lookup and mobile number validation. use after confirming the number format to retrieve network, reachability, and roaming status.
Connect any two apps with Notis in the middle.
Notion and Neutrino, 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 Neutrino.