Listen after customers adopt a feature
Shipping a feature is only the first signal. When customers begin using it, keep learning through an ongoing feedback cycle.
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
Add Person to Autopilot Email
Tool to add a person to Autopilot or update their properties for email-based surveys. Use when you need to enroll a person in scheduled email surveys or update their custom properties.
Why this helps
Feature adoption data may show that someone started, but it does not explain what they think or where they get stuck.
- Pair adoption milestones with customer sentiment.
- Build ongoing listening into the product learning loop.
- Avoid a separate enrollment task for each adopter.
Setup
Build it in a few focused steps.
- 1Connect Notion and Delighted to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to create it conversationally.
- 3Describe the adoption signal and how eligible customers should join Delighted Autopilot Email.
- 4Choose the Notion Page Properties Updated trigger and where to receive run reports.
- 5Test with one customer adoption record and confirm the enrollment.
Questions about this workflow
Does this measure feature usage?
No. It uses a Notion record as the cue to enroll a customer in Delighted feedback surveys.
Can the survey focus on one feature?
Include the feature context in the plain-language instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Delighted. A trigger fires from one place; an action lands in another.
Notion triggers
Delighted actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Person to Autopilot Email
Tool to add a person to Autopilot or update their properties for email-based surveys. Use when you need to enroll a person in scheduled email surveys or update their custom properties.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Person to Autopilot SMS
Tool to add a person to Autopilot or update their properties for SMS-based surveys. Use when you need to schedule automated survey delivery via SMS.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create or Update Person
Tool to create or update a person and schedule a survey email. Use when you need to add a new person to Delighted, update existing person details, or schedule a survey with custom properties for segmentation.
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 Pending Survey Requests
Tool to remove all pending (scheduled but not yet sent) survey requests for a person. Use when you need to cancel all future surveys for a specific email address.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Person
Tool to remove a person and all associated data from Delighted. Use when you need to permanently delete a person's information. Deletion includes surveys, responses, properties, Autopilot membership, survey history, and unsubscribe/bounce status.
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 Autopilot Email Configuration
Tool to retrieve the current Autopilot configuration for email distribution. Returns configuration details including whether Autopilot is active, survey frequency, and timestamps.
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 Autopilot SMS Configuration
Tool to retrieve the current Autopilot configuration for SMS distribution. Use when you need to check whether Autopilot is enabled, review survey frequency settings, or examine configuration timestamps for SMS surveys.
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 Autopilot SMS Memberships
Tool to retrieve all Autopilot memberships for SMS distribution platform. Use when you need to list people enrolled in Autopilot SMS or filter by specific person details.
Connect any two apps with Notis in the middle.
Notion and Delighted, 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 Delighted.