Ground feature requests in submitted feedback
A new feature request can cue Notis to retrieve relevant Formcarry responses, helping you consider the broader feedback before deciding what comes next.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Retrieve Form Submissions
Tool to retrieve a list of submissions for a specific form identified by its id. supports pagination to navigate through large sets of submissions.
Why this helps
A vivid individual request can dominate attention when related customer feedback is stored elsewhere.
- Adds broader response context to new requests.
- Supports calmer, evidence-informed prioritization.
- Reduces manual searches during product planning.
Setup
Build it in a few focused steps.
- 1Connect Notion and Formcarry to Notis once.
- 2Create an automation or ask Notis to retrieve and summarize relevant submissions from your feedback form when a feature request page is added to its database.
- 3Select New Page and scope it to the feature-request data source; choose a run-report channel.
- 4Add one test feature request and verify the retrieval.
Questions about this workflow
Can it match entries to an individual request?
Explain the matching context in the prompt. The action retrieves submissions for a specified form and does not guarantee a record-level match.
Will it prioritize the request automatically?
It can summarize response context, but the workflow does not create or update a prioritization record.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Formcarry. A trigger fires from one place; an action lands in another.
Notion triggers
Formcarry actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Retrieve Form Submissions
Tool to retrieve a list of submissions for a specific form identified by its id. supports pagination to navigate through large sets of submissions.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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 Formcarry, 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 Formcarry.