Validate Job Applicant Emails Automatically
Neurodivergent founders need reliable hiring pipelines. Stop losing great candidates to invalid emails--validate them instantly on application.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Email Validation
Tool to validate whether an email address is real and deliverable. use after collecting an email address to confirm deliverability.
Why this helps
Typos in applicant emails mean you cannot reach qualified candidates, leading to lost talent and delays in filling critical roles.
- Never lose a top candidate due to an invalid email address
- Streamline follow-up with qualified applicants
- Identify contact issues before the interview stage
Setup
Build it in a few focused steps.
- 1Connect your Notion candidate database and Abstract account to Notis.
- 2Ask Notis: 'When a new job application comes through and includes an email, validate that email address right away.'
- 3Trigger on 'New Page in Database' scoped to your candidates table.
- 4Choose your notification channel for validation results.
- 5Test by adding a fake candidate with an intentionally invalid email to confirm validation.
Questions about this workflow
What should I do if a candidate's email fails validation?
Notis will flag the record in Notion--you can then reach out through alternative contact methods (LinkedIn, phone) to verify their correct email.
Can I automatically mark candidates for review if their email is invalid?
Yes--set up a follow-up workflow to tag candidates with validation issues so you can prioritize manual follow-up.
Does this slow down my hiring process?
No--validation happens in seconds without blocking your workflow, and actually speeds up hiring by preventing wasted outreach attempts.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Abstract. A trigger fires from one place; an action lands in another.
Notion triggers
Abstract actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Validate IBAN
Tool to validate the format and country code of an iban number. use after collecting an iban to ensure it is correctly formatted.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Email reputation
Tool to enrich an email address with reputation and risk scoring data. use when you need to assess an address's deliverability and risk before outreach. use after confirming your api key is valid.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Email Validation
Tool to validate whether an email address is real and deliverable. use after collecting an email address to confirm deliverability.
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 Abstract, 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 Abstract.