Keep a weekly pulse on key GoSquared events
A scheduled event-count snapshot can make weekly product review easier to begin and help keep important signals from slipping off your radar.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Retrieve Event Counts
Tool to retrieve counts of event triggers over a specified time period. Use when you need to analyze event frequency for a site between two date-times.
Why this helps
Product signals can be easy to forget when checking event counts depends on remembering the right report each week.
- Build a lightweight weekly signal check.
- Reduce the effort of retrieving event counts manually.
- Bring product activity into a regular review rhythm.
Setup
Build it in a few focused steps.
- 1Connect Notion and GoSquared to Notis once through the portal.
- 2Create an automation in the portal or ask Notis for a recurring event-count pulse.
- 3Describe the GoSquared site, event types of interest, and reporting period in one instruction.
- 4Choose a weekly Notis cron schedule and a channel for run reports.
- 5Test one run and confirm the event counts match the signals you want to watch.
Questions about this workflow
Can I focus on selected events?
Describe the event types that matter in the prompt and review the first report for relevance.
Can this run only when a Notion review page is updated?
This version uses a recurring schedule. You can instead use an appropriate Notion event trigger if you want a change to cue the check.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Gosquared. A trigger fires from one place; an action lands in another.
Notion triggers
Gosquared actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Shared User
Tool to add a new shared user to a project. Use when inviting team members via their email address.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Remove shared user
Tool to remove a user from a GoSquared project. Use when you need to revoke a shared user's access to your site.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Account Shared Users
Tool to retrieve all team members that have access to a given project. Use after specifying the project to inspect user access.
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.
List Account Sites
Tool to list all projects/sites accessible to the authenticated account. Use when you need to retrieve the account's sites in either grouped or flat format.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Check API Token Validity and Scopes
Tool to check whether an API key is valid and retrieve its enabled scopes. Use when verifying API credentials before making further API calls.
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.
Retrieve Chat Conversation
Tool to retrieve a chat conversation by its ID. Use when you need the full conversation history after obtaining a chat session 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.
Retrieve Chat Messages
Tool to retrieve a list of messages from a chat conversation. Use after identifying the chatID via listing chat conversations to page through a chat's message history.
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.
Retrieve Chat Conversations
Tool to retrieve chat data for reporting purposes. Use when you need to list active chat conversations within a specific time window.
Connect any two apps with Notis in the middle.
Notion and Gosquared, 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 Gosquared.