Connect AimTell to Breathe HR
When something happens in AimTell, 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 AimTell to Breathe HR
Log employee sickness from an AimTell campaign response
Use an AimTell campaign response to start a Breathe HR sickness record after an authorized employee reports sick leave.
Review Breathe HR leave requests alongside AimTell campaign activity
On a schedule, retrieve leave requests for review alongside AimTell campaign activity, then report notable dates or follow-ups without approving requests.
Check sickness records during AimTell campaign operations
Retrieve recent Breathe HR sickness records on a schedule and send a concise operational review for campaign planning.
Create a Breathe HR employee record from an authorized AimTell onboarding submission
Use an authorized onboarding submission delivered through AimTell to create a new Breathe HR employee record when all required details are present.
Review pending employee changes before an AimTell campaign cycle
Retrieve Breathe HR change requests on a recurring schedule and report pending items for a timely HR review.
Review upcoming absences for AimTell campaign coverage
Retrieve Breathe HR absences on a schedule and summarize upcoming coverage considerations for campaign planning.
Find leave requests that need an HR follow-up
Review Breathe HR leave requests on a schedule and surface items that may need a follow-up, while leaving decisions to authorized staff.
Check an employee's leave history before campaign handoffs
Retrieve an employee's leave request history on a schedule or review run to help prepare an informed campaign handoff.
Review the Breathe HR team roster for AimTell campaigns
Retrieve the employee roster on a schedule and prepare a compact review to support campaign ownership and contact checks.
Supported Triggers and Actions
Notis builds workflows that link AimTell to Breathe HR. A trigger fires from one place; an action lands in another.
AimTell triggers
Breathe HR actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Approve Leave Request
Approve a pending employee leave request.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Employee
Create a new employee record.
Create Employee Change Request
Create a request to change an employee’s information.
Create Employee Expense
Record an employee expense for reimbursement or as a company-paid expense.
Create Employee Expense Claim
Group unclaimed expense records into a new reimbursement claim.
Create Employee Sickness
Create a record of an employee’s sickness absence.
Delete Employee Expense
Delete an employee expense record.
Delete Employee Training Course
Delete an employee training course record.
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 AimTell and Breathe HR
Connect any two apps with Notis in the middle.
AimTell 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.