Make a qualified lead feel remembered with a postcard
When a lead reaches your chosen qualification stage in Notion, let Notis send an approved postcard through Docupost.
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
Send Postcard
Tool to send a postcard via u.s. mail with specified recipient, sender, and front/back images. use after confirming recipient addresses and design urls. example: send postcard(to name='john doe', ..., front image='https://...', back image='https://...')
Why this helps
Sales follow-up can stall when qualification happens in one workspace and the personal gesture requires a separate mailing task.
- Connect qualification to a thoughtful next touch.
- Reduce manual handoffs between sales tracking and mail.
- Use a consistent postcard for the right stage.
Setup
Build it in a few focused steps.
- 1Connect Notion and Docupost to Notis once in the portal.
- 2Create an automation describing when a lead qualifies and which approved postcard to send.
- 3Select Page Properties Updated for the leads data source and choose a channel for run reports.
- 4Test with one real lead status update and verify address and image URLs before sending.
Questions about this workflow
How should I define qualified?
Use the qualification status already maintained in the Notion lead record and describe the intended status in the prompt. Test one status change to confirm the result.
Can I use a different card design?
Describe the approved front and back image URLs or design to use for this workflow, and verify them during the first run.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Docupost. A trigger fires from one place; an action lands in another.
Notion triggers
Docupost actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Send Letter
Tool to send a letter via u.s. mail with specified recipient, sender, and pdf. use after confirming recipient and document details. example: send letter(to name='john doe', to address='123 main st, ...', file url='https://...')
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Send Postcard
Tool to send a postcard via u.s. mail with specified recipient, sender, and front/back images. use after confirming recipient addresses and design urls. example: send postcard(to name='john doe', ..., front image='https://...', back image='https://...')
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 Docupost, 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 Docupost.