Recheck recipient details after page content changes
Keep a meaningful content change from slipping past the mailing check.
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
Important recipient details can change in page notes without a matching database property update or obvious follow-up task.
- Revisit details after relevant page content changes.
- Keep the validation result connected to the source notes.
- Help reduce missed checks when information lives in page text.
Setup
Build it in a few focused steps.
- 1Connect Notion and Lob to Notis once in the portal.
- 2Ask Notis to validate recipient name and address details from the updated page content when those details are present, then report the result.
- 3Choose the Notion Page Content Updated trigger scoped to the relevant page and select a reporting channel.
- 4Test by making a controlled edit to recipient details and reviewing the result.
Questions about this workflow
Will every page edit produce a validation?
The trigger aggregates page content edits. Phrase the prompt to check only when updated context includes usable recipient details.
Can this monitor several pages?
The trigger can be scoped to one page or to pages in a data source, depending on the available trigger configuration.
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.