Reduce manual steps in name-origin research
For research that explicitly permits name-origin estimates, let a Notion page change start the lookup and keep the result in context for careful review.
Trigger
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Action
Get Country of Origin
Tool to retrieve a name's likely countries of origin. Use after confirming the name identifier.
Why this helps
Small research checks can become a backlog when you are moving between participant notes, project work, and follow-ups.
- Catches eligible research pages across the workspace.
- Keeps the request tied to a stated research purpose.
- Makes the estimate available for review without treating it as verified background.
Setup
Build it in a few focused steps.
- 1Connect Notion and Gender API to Notis once.
- 2Create an automation in the portal or ask Notis to use Get Country of Origin only for pages explicitly marked eligible for name-origin research.
- 3Select the Notion All Page Events trigger and include the eligibility check in the instruction.
- 4Choose a channel for run reports, then test with one eligible page.
Questions about this workflow
Does country of origin mean nationality or ethnicity?
No. A name-based estimate does not establish a person's nationality, ethnicity, or personal background.
Should I act on the result for an individual?
No. Treat it as an uncertain signal for a properly consented, aggregate research question only.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Gender api. A trigger fires from one place; an action lands in another.
Notion triggers
Gender api actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Country of Origin
Tool to retrieve a name's likely countries of origin. Use after confirming the name identifier.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Gender API Statistics
Tool to retrieve account statistics from Gender-API, including remaining credits and usage details. Use when you need to check your credit balance before performing further gender lookups.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Query Gender by Email Address
Tool to determine gender from an email address. Use when you need the likely gender based on an email.
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.
Gender From First Name
Tool to determine the gender of a first name. Use when you need to identify gender based on a given name.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Query Gender by Full Name
Tool to determine gender by splitting a full name. Use when you have an exact full name string and want to infer gender. Slightly less reliable for rare or ambiguous names.
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 Gender api, 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 Gender api.