Connect campaign planning with response review
When a campaign brief arrives, have Notis prepare the relevant response context so follow-up is easier to plan.
Trigger
New Page
Triggers when a new page is added to a Notion database.
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
Campaign planning and form responses can live in separate places, making it difficult to see what needs attention.
- Bring response context closer to campaign planning.
- See whether submissions need a follow-up plan.
- Reduce manual back-and-forth between tools.
Setup
Build it in a few focused steps.
- 1Connect Notion and Getform to Notis once.
- 2Create an automation or ask Notis to retrieve submissions for the Getform form named in each new campaign brief and summarize response context.
- 3Select New Page and scope it to your campaign briefs data source.
- 4Choose a channel for run reports and test with one brief that identifies a form.
Questions about this workflow
Will a campaign page always include a form ID?
The Get Form Submissions action needs a specific form ID. Ensure the relevant context makes that ID available to Notis.
Does the workflow submit a campaign response?
No. It retrieves submissions for review. Submitting a new form response uses a different Getform 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.