Connect Breathe HR to Notion

When something happens in Breathe HR, Notis takes the next step in Notion. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Adds multiple content blocks to a Notion page or supported block; simplified text may be truncated.

Build an automation Browse examples

Examples

Ways Notis can move work from Breathe HR to Notion

Create a Notion onboarding hub from a Breathe HR request

Turn an onboarding request into a Notion page with the employee details and next steps provided in the request.

Log an absence request in a Notion database

Create a Notion database row from an absence request, using only the details supplied in the webhook request.

Add review context to an absence request page

Post a Notion comment with the review context supplied alongside an absence request, so it is easy to find on the relevant page.

Add onboarding steps to a Notion page in one go

Append a readable set of onboarding checklist content blocks to a specified Notion page from a request.

Refresh review details on a Notion page

Update supported properties on a specified Notion page with review details supplied in a Breathe HR request.

Archive a closed HR page in Notion

Archive a specified Notion page when a request confirms it is closed and ready to leave the active workspace.

Review a Notion HR follow-up database weekly

On a schedule, query a specified Notion database for rows matching criteria described in the automation prompt and surface follow-ups in the run report.

Scan Notion for HR pages to review

On a schedule, fetch accessible Notion pages and databases using a query you specify, then report likely HR items for review.

Review content on a specified Notion HR page

Fetch the direct child blocks of a specified Notion page on a schedule and summarize its supplied HR content in the run report.

Supported Triggers and Actions

Notis builds workflows that link Breathe HR to Notion. A trigger fires from one place; an action lands in another.

Breathe HR triggers

Notion actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Add multiple content blocks (bulk, user-friendly)

Adds multiple content blocks to a Notion page or supported block; simplified text may be truncated.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Add single content block to Notion page (Deprecated)

Deprecated: Adds content to a Notion page or block; requires access and permission to insert content.

ActionInstant

Append raw Notion blocks (advanced API)

Deprecated: Appends raw blocks to a Notion page or block.

ActionInstant

Archive Notion Page

Archives a page to the trash or restores it; workspace-level pages must be archived in the interface.

ActionInstant

Append code blocks (code, quote, equation)

Appends code, quote, or equation blocks; each code text field is limited to 2,000 characters.

ActionInstant

Create comment

Adds a comment to a page or an existing discussion thread.

ActionInstant

Append layout blocks (divider, TOC, columns)

Appends layout blocks, including dividers, tables of contents, breadcrumbs, or columns.

ActionInstant

Create Notion Database

Creates a database as a subpage of a specified parent page.

ActionInstant

Trigger Types

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 schedule (recurring or one-time), and a change in one of your Notis databases.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

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.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Scheduled triggers

Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.

Daily · 8:00Weekdays onlyOnce · Dec 13

Beta

Database triggers

Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.

Row addedProperty editedValue > limit

Why AI automation

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.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

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:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

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.