Keep support requests from piling up unseen
A recurring triage pass makes support manageable without keeping the inbox open all day.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Form Submissions
Tool to retrieve submissions for a specific form. Use when you have a form ID and need paginated, searchable submissions optionally including file URLs.
Why this helps
Support requests compete with deep work when they are checked constantly or get forgotten when checked rarely.
- Check requests at a predictable time.
- Surface urgent items for a human response.
- Avoid repeatedly reopening the same submission list.
Setup
Build it in a few focused steps.
- 1Connect Getform and Notion to Notis once.
- 2Create a scheduled automation or ask Notis to retrieve recent support submissions and prepare a triage list with urgent items highlighted.
- 3Select a recurring schedule that matches your response commitments and specify the support form.
- 4Choose where run reports should appear and test with a small set of real submissions.
Questions about this workflow
Does the workflow answer support requests?
No. It retrieves submissions and prepares a triage view so you can decide and respond.
Can it prioritize urgent requests?
Ask Notis to identify urgency using the information submitted, then review its assessment before taking action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Getform. A trigger fires from one place; an action lands in another.
Notion triggers
Getform actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Form Submission
Tool to retrieve a specific submission by its ID. Use when you have both form_id and submission_id and need that single record.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Form Submissions
Tool to retrieve submissions for a specific form. Use when you have a form ID and need paginated, searchable submissions optionally including file URLs.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Submit Form
Tool to submit form data and files to a Getform endpoint. Use when you need to post fields, files, optional reCAPTCHA or honeypot to a specific form ID.
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 Getform, 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 Getform.