Give subscriber review a monthly rhythm
A recurring lookup reduces the need to remember where subscriber review fits among the rest of your founder work.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List Subscribers
Tool to list newsletter subscribers. Use when you need to retrieve subscribers with optional field selection, sorting, and pagination.
Why this helps
Routine list reviews tend to slip when they depend on remembering an irregular admin task.
- Create a predictable time for a subscriber list check.
- Retrieve records without manually opening the dashboard.
- Get run visibility in a selected channel.
Setup
Build it in a few focused steps.
- 1Connect Notion and Hotspotsystem to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to perform a recurring subscriber check.
- 3Use one plain-language instruction to retrieve the subscriber list and summarize the run.
- 4Choose a monthly schedule and a channel for run reports.
- 5Test the workflow with one run and confirm the output meets your review needs.
Questions about this workflow
Does this workflow require a Notion event?
No. It uses a Notis recurring schedule as its trigger.
Can I retrieve subscribers for one location instead?
Yes. Choose the Hotspotsystem List Subscribers by Location action for a location-specific review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Hotspotsystem. A trigger fires from one place; an action lands in another.
Notion triggers
Hotspotsystem actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List Customers
Tool to list customers. Use when you need to retrieve customers with optional pagination, sorting, and field selection.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Customers by Location
Tool to list customers by location. Use when you need to retrieve customers for a specific location with optional field selection, sorting, and pagination.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Generate Voucher (v1)
Tool to generate an access voucher on the fly. Use when you need a single-use voucher for a specified location after ensuring sufficient credits.
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 Locations
Tool to list the resource owner's locations. Use when you need to retrieve locations with optional filtering, sorting, or pagination.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Misc Ping
Tool to perform health check against the HotspotSystem API. Use when verifying connectivity and availability.
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.
List Subscribers
Tool to list newsletter subscribers. Use when you need to retrieve subscribers with optional field selection, sorting, and pagination.
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.
List Subscribers by Location
Tool to list subscribers by location. Use when you need to retrieve subscribers for a specific location with optional field selection, sorting, and pagination.
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.
List MAC Transactions
Tool to list MAC-based transactions. Use when you need to retrieve MAC transaction records with optional pagination and sorting.
Connect any two apps with Notis in the middle.
Notion and Hotspotsystem, 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 Hotspotsystem.