Estimate a name from an intake webhook
Let an existing intake system cue a small research estimate without requiring another manual handoff.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Custom intake processes can leave founders with an extra lookup step after the record has already arrived.
- Connect an existing intake event to a reviewable estimate.
- Reduce a manual handoff after form submission.
- Keep confidence visible in run reports.
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 conversationally, then choose an incoming webhook trigger.
- 3Give one plain-language instruction to use the first name supplied by the intake request, request an estimate, and report confidence for aggregate review.
- 4Choose where Notis should send run reports and configure your backend to call the generated webhook.
- 5Test by sending one real intake example and inspect the report.
Questions about this workflow
Does this webhook come from Notion?
It is a Notis-native incoming webhook trigger for a custom backend. The instruction can use context associated with Notion and the incoming request.
Should the result be used to make an individual decision?
No. The estimate is uncertain and should only support carefully reviewed aggregate research.
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.