Keep feedback collection settings aligned with the plan
When a feedback record changes status, check the deployment details so collection rules remain visible alongside the decision.
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
Get Deployment by ID
Retrieves detailed configuration for a specific feedback form deployment by its ID. Returns deployment rules, trigger conditions, scheduling settings, target URLs, and active status. Use this to understand when, where, and how a feedback form is displayed to users.
Why this helps
Feedback status changes can leave teams unsure whether the live form's rules and target locations still match the plan.
- Bring live deployment context into status reviews.
- Help spot when collection settings need human attention.
- Reduce the risk of relying on outdated assumptions.
Setup
Build it in a few focused steps.
- 1Connect Notion and Mopinion to Notis once through the portal.
- 2Create an automation prompt to retrieve relevant deployment details when a feedback tracking record changes.
- 3Select the Notion Page Properties Updated trigger, scoped to the feedback tracking data source if appropriate.
- 4Choose a reporting channel and test with a representative status update.
Questions about this workflow
Will it update the deployment status?
No. It retrieves configuration details for review and does not change deployment settings.
Can it respond to a particular status property?
Describe the status field in the prompt. The Notion event provides updated property information for Notis to consider.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Mopinion. A trigger fires from one place; an action lands in another.
Notion triggers
Mopinion actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Account
Tool to retrieve the current authenticated account information. Use to verify authentication and get account details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Dataset by ID
Retrieve complete metadata for a specific Mopinion dataset (feedback form) by its ID. Returns dataset properties including name, associated report ID, data source type, and description. Use this action when you need detailed information about a specific dataset/form. To discover available dataset IDs, use the List Datasets action first. This is a read-only operation that does not modify any data.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Dataset Feedback
Retrieve feedback items (survey responses) for a specific dataset/form with optional pagination and filtering. Use this action to fetch multiple feedback entries from a dataset. Each feedback item contains the survey responses including custom fields, scores, metadata, and timestamps. Supports pagination for large result sets and filtering by field values. For retrieving a single feedback item by ID, use GET_DATASET_FEEDBACK_BY_ID instead.
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.
Get Dataset Feedback By ID
Retrieves a single feedback item by its unique identifier from a specific dataset. Use this tool when you need detailed information about a specific feedback item. First obtain the dataset_id using List Datasets, then get feedback_id values using Get Dataset Feedback. **Important Notes:** - Returns a warning in metadata if the feedback item doesn't exist (with null field values) - Returns 404 error if the dataset_id itself is invalid or inaccessible - The response includes feedback fields, tags, scores, timestamps, and associated metadata
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Dataset Field Definitions
Tool to retrieve field definitions for a dataset. Use when you need the schema of a dataset's fields.
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 Deployment by ID
Retrieves detailed configuration for a specific feedback form deployment by its ID. Returns deployment rules, trigger conditions, scheduling settings, target URLs, and active status. Use this to understand when, where, and how a feedback form is displayed to users.
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 Deployments
Tool to list all deployments for the authenticated Mopinion account. Use after setting up authentication.
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.
Get Report By ID
Retrieves detailed information about a specific Mopinion report by its ID. Returns comprehensive report details including name, description, language, creation date, and all associated datasets with their metadata. Use this when you need full information about a specific report. To find available report IDs, use the Get Reports action first. Example use case: Get complete details of report 22511 to understand its datasets and configuration.
Connect any two apps with Notis in the middle.
Notion and Mopinion, 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 Mopinion.