Check consent before an email lookup
A consent-aware instruction helps prevent email enrichment from becoming an unchecked default. Notis can inspect a new page, verify the notes say proper consent is in place, and report a likely result for review.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Query gender by email address
Tool to determine gender from an email address. Use when you need to infer gender for personalization after obtaining proper consent.
Why this helps
When contact capture is quick, consent context can be missed before enrichment begins.
- Makes documented consent a condition of the lookup.
- Starts from a newly created Notion page.
- Returns a reviewable result rather than silently asserting identity.
Setup
Build it in a few focused steps.
- 1Connect Notion and GenderAPI.io to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Use one plain-language instruction asking Notis to query a contact email only when proper consent is documented, then report the likely result for review.
- 4Choose the Notion Page Created trigger and a channel for run reports.
- 5Test with a sample record that clearly documents consent.
Questions about this workflow
What happens if the page does not mention consent?
Tell Notis to skip the lookup and report that consent was not documented.
Can the result be used to address a person?
Do not assume a person's pronouns or identity from an inferred result. Review it and follow the person's stated preferences.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Genderapi io. A trigger fires from one place; an action lands in another.
Notion triggers
Genderapi io actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Gender API Get Statistics
Tool to retrieve account usage statistics from GenderAPI.io. Use when you need to check remaining API credits and expiry.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Query Gender by First Name
Tool to determine gender by querying first name. Use when you need to infer likely gender for a given name with optional localization hints.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Gender from Username
Tool to determine gender from a username or nickname. Use when you have an alias or handle and want to infer gender from that identifier.
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.
List Gender API Error Codes
Tool to list all possible error codes returned by Gender API. Use when debugging or validating API responses.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Query gender by email address
Tool to determine gender from an email address. Use when you need to infer gender for personalization after obtaining proper consent.
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.
Query Gender by Full Name
Tool to determine gender from a full name. Extracts the first valid name token and queries the GenderAPI.io single-name endpoint. Use when you have a full name and want to infer likely gender.
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 Genderapi io, 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 Genderapi io.