Turn a ready expense batch into a Breathe HR claim
Give expense batches a clear next step by using their Notion ready status to start claim creation.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
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.
Why this helps
Expense records may be entered but never grouped into a claim, leaving reimbursement follow-up as another open loop.
- Close the gap between expense capture and claim submission
- Use one batch-ready signal to prompt the next step
- Reduce the mental load of tracking which expenses still need claiming
Setup
Build it in a few focused steps.
- 1Connect Notion and Breathe HR to Notis once through the portal.
- 2Create an automation or tell Notis to create a Breathe HR expense claim from the relevant unclaimed expenses when a Notion batch is marked ready.
- 3Choose Page Properties Updated for the expense batch data source and select a run report channel.
- 4Test with a real batch and confirm the resulting claim and included expenses in Breathe HR.
Questions about this workflow
Does a Notion batch itself become the claim?
The action creates a Breathe HR claim by grouping one or more unclaimed expense records. Explain in the prompt which expenses the batch refers to.
Can it submit every expense automatically?
The instruction should clearly identify which batch is ready, so Notis can act only on the expenses intended for that claim.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Breathe HR. A trigger fires from one place; an action lands in another.
Notion 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.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
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.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Delete Employee Expense
Tool to delete an employee expense by ID. Use when you need to remove an expense record from the system.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
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.
Connect any two apps with Notis in the middle.
Notion 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.