Ask for customer feedback at a success checkpoint
Let the checkpoint you document start a feedback request, without another reminder on your task list.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Send GatherUp Customer Feedback
Tool to send a feedback request to a customer. Use when prompting customers for feedback after an interaction. Ensure a valid hash signature is provided.
Why this helps
A customer success plan can track internal actions well while leaving the customer's own view unasked.
- Tie feedback requests to meaningful customer checkpoints.
- Make follow-up consistent across customer plans.
- Reduce extra task tracking for service reviews.
Setup
Build it in a few focused steps.
- 1Connect Notion and Gatherup to Notis once in the portal.
- 2Create an automation through Automations or by asking Notis conversationally.
- 3Write one plain-language instruction describing which new success plan or checkpoint should cause Gatherup to request feedback.
- 4Select Page Created as the trigger, choose your reporting channel, and test with one real customer plan.
Questions about this workflow
Can the workflow run only for a completed checkpoint?
State which checkpoint condition should qualify in your prompt and validate using an example page.
Does creating a page always send a request?
The trigger detects page creation; the instruction should define which success plan pages should prompt a request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Gatherup. A trigger fires from one place; an action lands in another.
Notion triggers
Gatherup actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete GatherUp Business
Tool to delete an existing business location. Use when you need to remove a business after validating its ID and signature.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Generate GatherUp Hash Signature
Tool to generate a SHA-256 hash signature required by GatherUp endpoints. Signature rule (commonly documented by GatherUp): SHA-256 over: privateKey + concatenation of all request parameter key-value pairs (excluding 'hash'), ordered alphabetically by key. Include clientId when present.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get GatherUp Business
Tool to get business details by business ID. Use when you have clientId and valid hash to retrieve a business location record.
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 GatherUp Business Types
Tool to get business types. Use to fetch available business type identifiers after generating a valid hash signature; optionally filter by search term.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get GatherUp Customer
Tool to get customer details by ID. Endpoint: POST /customer/get
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.
Search GatherUp Business
Tool to find business ID by customField or extraField. Endpoint: POST /business/search
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.
Send GatherUp Customer Feedback
Tool to send a feedback request to a customer. Use when prompting customers for feedback after an interaction. Ensure a valid hash signature is provided.
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 Gatherup, 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 Gatherup.