Skip to content
Notis

Review a localized name list from Notion

When a localized research list changes, request estimates in one small batch and keep results ready to inspect.

Trigger

Page Updated

Triggers when any block within a specified Notion page is updated.

Action

Batch Predict Gender with Localization

Tool to predict genders for a batch of names with optional country localization. Use after gathering 1-10 first names when needing localized gender estimates by country.

Why this helps

Maintaining a regional list can turn into repeated lookups that interrupt a founder's main work.

  • Handle up to ten listed first names together.
  • Use country context described in the page when available.
  • Reduce repeated tool switching during regional research.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Genderize to Notis once through the portal.
  • 2Create an automation in Automations, or ask Notis for the flow conversationally.
  • 3Give one instruction to use only the explicitly listed first names and country context, request localized estimates for up to ten names, and report confidence.
  • 4Select Page Updated for the relevant Notion page and choose a channel for reports.
  • 5Test by updating the page with one real name and country context.

Questions about this workflow

What if the page contains more than ten names?

The action is intended for batches of one to ten names. The instruction can ask Notis to process a small batch and report if the list exceeds that limit.

Does country context guarantee accuracy?

No. It helps localize a probabilistic estimate but does not make it definitive.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Notion to Genderize. A trigger fires from one place; an action lands in another.

Notion triggers

Genderize actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Predict Gender

Tool to predict gender from a given first name. Use when you need a quick gender estimation possibly localized by country code.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Predict Gender Batch

Tool to predict gender for multiple names in a single request. Use when batch gender predictions for several names at once.

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

Batch Predict Gender with Localization

Tool to predict genders for a batch of names with optional country localization. Use after gathering 1-10 first names when needing localized gender estimates by country.

ActionInstant

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.

TriggerInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

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.

TriggerInstant

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.

TriggerInstant

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.

TriggerInstant

Connect any two apps with Notis in the middle.

Notion and Genderize, 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 Genderize.