Collect event feedback without a manual reminder
Let the event record start the follow-up while you are already wrapping up logistics.
Trigger
New Page
Triggers when a new page is added to a Notion database.
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
After an event, the founder is juggling receipts, leads, and next steps, so attendee feedback gets delayed.
- Prompt for event feedback while the experience is recent.
- Make post-event follow-up easier to repeat.
- Reduce the number of wrap-up tasks you need to remember.
Setup
Build it in a few focused steps.
- 1Connect Notion and Gatherup through the Notis portal once.
- 2Create the automation in the portal or tell Notis the outcome in a message.
- 3Use one plain-language instruction describing which newly created event records should start a Gatherup feedback request.
- 4Pick New Page as the trigger, select a run-report channel, and test with one real event record.
Questions about this workflow
Can this apply only to completed events?
State in the prompt that only records for completed events should result in a request.
What does the customer receive?
Gatherup sends a customer feedback request according to the connected account and action setup.
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.