Connect Abstract to Breathe HR

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

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Abstract to Breathe HR

View example

Create a Breathe HR employee after contact checks

Validate a new hire's email and phone details with Abstract, then create their Breathe HR employee record from the submitted onboarding information.

View example

Approve a leave request after a text review

Have Abstract process a submitted leave review note, then approve the specified pending Breathe HR request when the instruction confirms it is authorized.

View example

Record a reasoned leave decline in Breathe HR

Process a submitted decision note with Abstract and reject the identified Breathe HR leave request when an authorized decline and reason are supplied.

View example

Create a checked employee expense from an intake

Process a submitted expense description with Abstract and create a Breathe HR expense record using the amount, date, employee, and details provided.

View example

Log a sickness report after intake review

Process an incoming sickness report with Abstract and create a Breathe HR sickness record when the employee, dates, type, and status are supplied.

Supported Triggers and Actions

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

Abstract triggers

Breathe HR actions

Recurring trigger

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

TriggerScheduled

Approve Leave Request

ActionInstant

Webhook trigger

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

TriggerInstant

Create Employee

ActionInstant

Create Employee Change Request

ActionInstant

Create Employee Expense

ActionInstant

Create Employee Expense Claim

ActionInstant

Create Employee Sickness

ActionInstant

Delete Employee Expense

ActionInstant

Delete Employee Training Course

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 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.

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

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

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.

Row insertedValue > limitQuery match

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.