Connect Clickup to Breathe HR
When something happens in Clickup, 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
Ways Notis can move work from Clickup to Breathe HR
Create a Breathe HR employee from a ClickUp onboarding task
Turn a completed employee onboarding task into a new Breathe HR employee record.
Approve Breathe HR leave when a ClickUp task reaches approval
Use a ClickUp status change to approve the matching pending leave request in Breathe HR.
Reject Breathe HR leave from a ClickUp decision
When a ClickUp leave task is rejected, decline the corresponding Breathe HR request with the recorded reason.
Turn a ClickUp HR comment into a Breathe HR change request
Create a formal Breathe HR employee change request from an authorized ClickUp task comment.
Review employee change requests when ClickUp ownership changes
Check an employee's Breathe HR change requests when a ClickUp people task is reassigned.
Check Breathe HR leave details when ClickUp dates change
Retrieve the matching leave request when a ClickUp task's dates are changed.
Log sickness in Breathe HR from a ClickUp report
Create a Breathe HR sickness record from a structured ClickUp comment about an employee absence.
Update a Breathe HR sickness record from a revised ClickUp comment
Apply corrected sickness dates or status from an edited ClickUp comment to Breathe HR.
Find the Breathe HR employee behind a ClickUp new hire task
Retrieve the matching Breathe HR employee record when a new hire task is created.
Supported Triggers and Actions
Notis builds workflows that link Clickup to Breathe HR. A trigger fires from one place; an action lands in another.
Clickup triggers
Breathe HR actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Approve Leave Request
Tool to approve a leave request in BreatheHR. Use when an authorized user needs to approve a pending leave request.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Employee
Tool to create a new employee in BreatheHR. Use when you need to add a new employee record with their personal information, contact details, and employment information. Required fields are first_name, last_name, email, and company_join_date.
Folder Created
Triggers when a new Folder is created.
Create Employee Change Request
Tool to create a change request for an employee field. Use when you need to update employee information such as job title, department, or salary.
Folder Deleted
Triggers when a Folder is deleted.
Create Employee Expense
Tool to create an employee expense record in BreatheHR. Use when an employee needs to submit a new expense claim for reimbursement or record a company-paid expense.
Folder Updated
Triggers when a Folder is updated (renamed, content edited, etc.).
Create Employee Expense Claim
Tool to create a new expense claim for an employee. Use when you need to submit expenses for reimbursement by grouping one or more unclaimed expense records into a claim.
List Created
Triggers when a new List is created.
Create Employee Sickness
Tool to create a sickness record for an employee in BreatheHR. Use when you need to log an employee's sick leave with details like type, dates, and status.
List Deleted
Triggers when a List is deleted.
Delete Employee Expense
Tool to delete an employee expense by ID. Use when you need to remove an expense record from the system.
List Updated
Triggers when a List is updated (renamed, content edited, etc.).
Delete Employee Training Course
Tool to delete an employee training course record by its ID. Use when you need to remove a training record from an employee's profile.
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 Clickup and Breathe HR
Connect any two apps with Notis in the middle.
Clickup and Breathe HR, 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 Breathe HR.