Connect Google Docs to Breathe HR
When something happens in Google Docs, 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 Google Docs to Breathe HR
Create a Breathe HR employee from a new Google Doc
Turn a newly created hiring document into a complete Breathe HR employee record.
Create an employee when an onboarding template is filled
Use a completed Google Docs onboarding template to create the matching Breathe HR employee.
Turn policy document updates into employee change requests
Detect matching Google Docs updates and create Breathe HR change requests for approved employee changes.
Create change requests from updated review documents
When a review document changes, ask Notis to create the relevant Breathe HR employee change request.
Log sickness when a keyword appears in a Google Doc
Create a Breathe HR sickness record when an authorized sickness keyword is detected.
Log sickness when a document reaches a threshold
Use a Google Doc word threshold to prompt a Breathe HR sickness record from a detailed absence note.
Update training records after a course document changes
When a training document gains or loses structured content, update the matching Breathe HR training course.
Update sickness records from return-to-work documents
Monitor matching Google Docs updates and update Breathe HR sickness records with review details.
Create an employee expense from a new expense brief
Turn a newly created Google Doc expense brief into a Breathe HR employee expense record.
Supported Triggers and Actions
Notis builds workflows that link Google Docs to Breathe HR. A trigger fires from one place; an action lands in another.
Google Docs 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.
New Document Created
Triggers when a new Google Doc is created. This trigger monitors Google Docs and fires when new documents are detected. Uses timestamp filtering to efficiently poll for new documents.
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.
Document Deleted
Triggers when an existing Google Doc is deleted (moved to trash). This trigger monitors Google Docs and fires when documents are trashed.
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.
Document Placeholder Filled
Triggers when a Google Doc's plain text changes such that a configured placeholder token/pattern is no longer present (i.e., the document has been filled in). This trigger monitors a specific Google Doc and fires when a placeholder pattern that was previously present is no longer found in the document's plain text.
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.
Document Search Update
Triggers when a Google Doc matching a user-defined search query is newly created or updated since the last poll. This trigger uses timestamp filtering to efficiently monitor documents.
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.
Document Structure Changed
Triggers when a Google Doc's structure changes (headers/footers added/removed, tables/images count changes). This trigger monitors a specific document for structural changes like: - Headers added or removed - Footers added or removed - Tables added or removed - Images (inline objects) added or removed - Positioned objects added or removed - Footnotes added or removed
Delete Employee Expense
Tool to delete an employee expense by ID. Use when you need to remove an expense record from the system.
Document Updated
Triggers when an existing Google Doc is updated or modified. This trigger monitors Google Docs and fires when documents are updated.
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 Google Docs and Breathe HR
Connect any two apps with Notis in the middle.
Google Docs 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.