Connect Notion to Heartbeat
When something happens in Notion, Notis takes the next step in Heartbeat. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Notion to Heartbeat
Check Heartbeat events from a Notion planning item
When a new event-planning page is added to Notion, retrieve Heartbeat events so you can compare the community calendar before announcing another date.
Find Heartbeat channels for a new community guide
When a community guide page is created in Notion, retrieve Heartbeat channels to help identify where the guide belongs before sharing it.
Review Heartbeat members when onboarding status changes
When a Notion onboarding record changes, list Heartbeat users to help verify community membership during a member handoff.
Pull event context after a Notion comment
When someone comments on an event-planning page in Notion, retrieve Heartbeat events so the discussion has current calendar context.
Review Heartbeat channels after a Notion resource update
When the body of a Notion resource page changes, list Heartbeat channels to help you revisit where that resource is shared.
Check Heartbeat groups for a new Notion subpage
When a subpage is added beneath a community onboarding page, list Heartbeat groups to support a thoughtful access and orientation review.
Review Heartbeat channels when a Notion view is created
When a new Notion view is created, list Heartbeat channels to help connect a new planning lens with the right community spaces.
Check Heartbeat groups for a new Notion database
When a new Notion database container is created, retrieve Heartbeat groups to support a quick check for related community spaces.
Review Heartbeat groups when a Notion data source appears
When a Notion data source is created, retrieve Heartbeat groups so you can consider the community structure alongside the new data source.
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.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Notion and Heartbeat
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.