Catch email format mistakes during contact updates
Update a contact in Notion and let Encodian check the email address format, so follow-up is less likely to stall over a simple typo.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Validate Email Address
Tool to validate an email address. Use when checking email formats against a custom regex before processing user inputs.
Why this helps
An email entered incorrectly can quietly derail a founder's follow-up plan and lead to repeated attempts to reach the wrong address.
- Catch malformed email addresses near the point of update.
- Reduce avoidable follow-up retries.
- Keep contact cleanup out of the urgent task queue.
Setup
Build it in a few focused steps.
- 1Connect Notion and Encodian to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to validate the email when a contact record is updated.
- 3Select the Notion Page Properties Updated trigger for the contacts database.
- 4Choose a channel for run reports and test with a valid and an intentionally malformed email.
Questions about this workflow
Does validation confirm the person owns the address?
No. The Encodian action validates an email address against a custom regex; it does not confirm ownership or inbox delivery.
Will every property update run the check?
The trigger fires when page properties are updated. Describe the intended email-check behavior in the plain-language prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Encodian. A trigger fires from one place; an action lands in another.
Notion triggers
Encodian actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Decode Base64 String
Tool to decode a Base64 string to a file. Use when you need to extract binary content (e.g., PDF, image) from Base64 data.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Base64 Encode
Tool to encode a string to Base64. Use when you need to convert text into Base64 representation for use in other operations.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Compare Text
Tool to compare two text strings and determine if they match. Use when you have two strings and need to verify if they are equal.
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.
Hash Data
Tool to compute a cryptographic hash (MD5, SHA256, etc.) of text or file data. Use when you need to verify integrity or generate digests.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Unzip File
Tool to extract files from an archive. Use when you need to unzip a package and retrieve its contents.
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.
Get File Properties
Tool to retrieve properties of a file. Attempts multiple Encodian Filer endpoints and fallbacks.
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.
Resize Image
Tool to resize an image by percentage or dimensions. Use when you need to scale or reshape an image with optional aspect-ratio enforcement.
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.
Move File
Tool to move a file between containers. Use when you need to relocate a blob within your storage without manually copying then deleting.
Connect any two apps with Notis in the middle.
Notion and Encodian, 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 Encodian.