Find the right Heartbeat channel for a Notion guide
A new guide can prompt a quick channel review, so you do not have to browse the community from scratch.
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
List channels
Tool to retrieve a paginated list of channels in the community. Use when you need to list, browse, or search for channels in the Heartbeat community. Supports filtering by archived status, channel type, and pagination.
Why this helps
Useful guidance can sit unpublished because finding the right community channel becomes another task to remember.
- Review available channels when a guide is ready.
- Spend less time browsing Heartbeat manually.
- Keep channel choice deliberate before posting.
Setup
Build it in a few focused steps.
- 1Connect Notion and Heartbeat to Notis once through the portal.
- 2Create an automation in the portal or describe it to Notis conversationally.
- 3Write one plain-language instruction to list Heartbeat channels when a community guide page is created in Notion.
- 4Choose the Notion Page Created trigger, select a run-report channel, and test with a real guide page.
Questions about this workflow
Will the guide be posted automatically?
No. This workflow lists channels; it does not post messages or publish the Notion page.
What does the channel list help with?
It gives you current Heartbeat channel information to consider while deciding where to share the guide.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Heartbeat. A trigger fires from one place; an action lands in another.
Notion triggers
Heartbeat actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Events
Tool to retrieve event information from the community. Use when you need to list events with optional pagination support.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List channels
Tool to retrieve a paginated list of channels in the community. Use when you need to list, browse, or search for channels in the Heartbeat community. Supports filtering by archived status, channel type, and pagination.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Groups
Tool to retrieve a paginated list of access groups in the community. Use when you need to browse groups with optional filters for parent groups or user membership. Supports cursor-based pagination.
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 Users
Tool to retrieve a paginated list of users in the Heartbeat community. Use when you need to get user information with optional filtering by creation date, group membership, or role.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Reactivate User
Tool to reactivate a previously deleted user by email to allow them to access the community again. Use when you need to restore access for a user who was previously removed.
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 Group
Tool to retrieve a single group by its ID. Use when you need to get detailed information about a specific group in the Heartbeat community.
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 User
Tool to retrieve a single user by their ID. Use when you need to get detailed information about a specific user in the Heartbeat community.
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 Heartbeat, 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 Heartbeat.