Estimate a contact name after a Notion update
Use a meaningful contact update as a cue to request one estimate and keep the next research step visible.
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
Predict Gender
Tool to predict gender from a given first name. Use when you need a quick gender estimation possibly localized by country code.
Why this helps
Small updates can create hidden admin chores when the founder has to remember a separate name research step.
- Attach a small research follow-up to a record change.
- Avoid revisiting updated contacts to remember what to do next.
- Keep confidence information alongside the run report.
Setup
Build it in a few focused steps.
- 1Connect Notion and Genderize to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to create it conversationally.
- 3Use one instruction to request an estimate only for an explicitly provided first name on a relevant contact update and report confidence.
- 4Select Page Properties Updated for the contact data source and choose a reporting channel.
- 5Test with one real contact update and review the result.
Questions about this workflow
Will any property change cause an estimate?
The event can fire on property updates. State in the prompt which kinds of changes are relevant and require an explicit first name.
Can I use this to profile a specific contact?
Use estimates only as uncertain aggregate research signals, not for individual profiling or decisions.
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.
Predict Gender
Tool to predict gender from a given first name. Use when you need a quick gender estimation possibly localized by country code.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Predict Gender Batch
Tool to predict gender for multiple names in a single request. Use when batch gender predictions for several names at once.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
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 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.