Connect Acculynx to Breathe HR

When something happens in Acculynx, 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 Acculynx to Breathe HR

View example

Turn an AccuLynx staffing request into an employee record

Start a Breathe HR employee record from an AccuLynx staffing request that includes the required new hire details.

View example

Route project role changes into Breathe HR

Create a Breathe HR change request when an AccuLynx update explicitly calls for an employee role or department change.

View example

Check a leave request mentioned in project coordination

Look up a specific Breathe HR leave request when an AccuLynx project update raises a scheduling question.

View example

Approve leave only from an explicit authorized instruction

Approve a specific pending Breathe HR leave request when the webhook carries an explicit approval from an authorized user.

View example

Record a project-reported sickness in Breathe HR

Create a sickness record from an explicit absence report that includes the employee and sickness dates and details.

View example

Review upcoming leave for project planning

On a recurring schedule, list leave requests for a date range and prepare a concise planning summary.

View example

Prepare a recurring absence coverage review

List Breathe HR absences on a schedule and summarize employee, date, and type details for workforce coverage review.

View example

Prepare a scheduled employee roster for project coordination

Retrieve the Breathe HR employee list on a schedule and prepare a concise roster for staffing review.

Supported Triggers and Actions

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

Acculynx 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

Approve a pending employee leave request.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Employee

Create a new employee record.

ActionInstant

Create Employee Change Request

Create a request to change an employee’s information.

ActionInstant

Create Employee Expense

Record an employee expense for reimbursement or as a company-paid expense.

ActionInstant

Create Employee Expense Claim

Group unclaimed expense records into a new reimbursement claim.

ActionInstant

Create Employee Sickness

Create a record of an employee’s sickness absence.

ActionInstant

Delete Employee Expense

Delete an employee expense record.

ActionInstant

Delete Employee Training Course

Delete an employee training course record.

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.