Validate Event Attendee Emails on Registration
Neurodivergent founders running events cannot afford comm failures. Stop sending event details to bad emails--validate them on registration.
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
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
Event announcements and logistics fail silently when attendee emails are typos or invalid, leaving people confused or missing the event.
- Ensure event communications reach every registered attendee
- Reduce no-shows from attendees who missed logistics emails
- Catch registration errors before event day
Setup
Build it in a few focused steps.
- 1Connect your Notion event registration database and Abstract account to Notis.
- 2Tell Notis: 'When someone registers for my event and enters their email, validate that email address immediately.'
- 3Set trigger to 'Page Created' on your event attendees database.
- 4Select your notification channel for validation alerts.
- 5Test by registering a dummy attendee with an intentionally invalid email address.
Questions about this workflow
Can I send a follow-up message to attendees with invalid emails asking them to correct it?
Yes--set up a follow-up automation that creates a Notion task or notifies you to reach out to that attendee before the event.
What if someone's email is valid but they do not receive event emails?
This automation validates deliverability, so if someone's email bounces, you will know it is not a typo and can investigate spam filtering or ISP issues.
Can I export a clean attendee list after validation?
Yes--after validation completes, you can filter your Notion database to show only attendees with verified emails and export that list.
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.