Check mailing details in updated notes
Keep key recipient notes from getting buried in a page edit.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Validate Identity
Tool to validate whether a given name is associated with an address. Use when you need to verify identity information by checking if a recipient name matches address records.
Why this helps
Founders who track correspondence in notes may forget to rerun a check when the details change in page text.
- Include recipient details written in page notes in the review process.
- Revisit the identity association when relevant content changes.
- Bring the outcome to a chosen reporting channel.
Setup
Build it in a few focused steps.
- 1Connect Notion and Lob to Notis once through the portal.
- 2Ask Notis to validate recipient identity details from the updated mailing notes when present and report if anything needs confirmation.
- 3Select the Notion Page Content Updated trigger scoped to the mailing page and choose a run-report channel.
- 4Test by updating a recipient detail in the page and reviewing the result.
Questions about this workflow
Will any edit on the page trigger this?
The page content trigger reports content updates. The prompt should ask Notis to proceed only when relevant recipient details are available.
Can it edit the notes based on the result?
This workflow only requests validation and reporting. It does not ask for page changes.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Lob. A trigger fires from one place; an action lands in another.
Notion triggers
Lob actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Domain
Tool to add a new custom domain for creating custom links. Use when you need to register a domain for short link customization.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Link
Tool to create a shortened URL from a long URL using Lob's link shortening service. Use when you need to shorten a long URL either by using a custom domain or Lob's own short domain.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Domain
Tool to delete a registered domain. Use only after confirming all associated links with the domain are deleted.
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.
Delete Link
Tool to delete a shortened link. Use when you need to remove a previously created short link from the system.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Upload
Tool to delete an existing upload by its unique identifier. Use when you need to permanently remove an upload and its associated data.
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 Domain
Tool to retrieve details for a single domain from Lob. Use when you need to get configuration status, redirect links, or other metadata for a specific domain.
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.
Get Link
Tool to retrieve a single shortened link. Use when you need to fetch details about a specific link by its ID.
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.
List Domains
Tool to retrieve a list of all created domains. Use when you need to view or manage custom domains configured for URL shortening. Supports pagination and filtering by configuration status.
Connect any two apps with Notis in the middle.
Notion and Lob, 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 Lob.