Check referral emails as they arrive
Let your referral intake send an HTTP request to Notis, then have Mailboxlayer check the address and report the result.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Check Email Validity
Tool to validate a single email address. use when you need to check syntax, domain, smtp, and meta-flags.
Why this helps
Referral details can arrive from different places, making it easy to miss a typo before the first reply.
- Check referral addresses at intake time.
- Reduce manual copy and paste into a separate validator.
- Keep a visible result for deciding the next outreach step.
Setup
Build it in a few focused steps.
- 1Connect Mailboxlayer to Notis once; connect Notion too if the referral context is stored there.
- 2Create a Notis automation in the portal or ask Notis conversationally, using a webhook trigger.
- 3Write one plain-language instruction asking Notis to validate the submitted referral email and report the result.
- 4Choose a channel for run reports and configure your intake system to send its request to the automation webhook.
- 5Test with one real referral submission.
Questions about this workflow
Can this use an external form?
Yes. A Notis webhook trigger starts when an external tool or custom backend sends an HTTP request.
Does the webhook send a reply to the referrer?
The selected action checks the email address. Use the run report to review the result.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Mailboxlayer. A trigger fires from one place; an action lands in another.
Notion triggers
Mailboxlayer actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Email Validity
Tool to validate a single email address. use when you need to check syntax, domain, smtp, and meta-flags.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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 Mailboxlayer, 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 Mailboxlayer.