Turn a Notion order approval into a Lexoffice confirmation
Once an order is approved, move its documentation forward without adding another manual handoff to your day.
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 Order Confirmation
Tool to create an Order Confirmation in Lexoffice/Lexware. Order confirmations are always created in draft mode and do not need to be finalized. Use when you need to confirm a customer order with line items, pricing, and shipping details.
Why this helps
Order approvals can sit unnoticed when confirmation paperwork depends on someone remembering a second step.
- Tie order confirmation preparation to the approval moment.
- Reduce follow-up tasks after a decision is made.
- Keep a consistent bridge between sales records and accounting.
Setup
Build it in a few focused steps.
- 1Connect Notion and Lexoffice to Notis once through the portal.
- 2Ask Notis to create a Lexoffice order confirmation when an order is marked approved in Notion.
- 3Select Page Properties Updated for the order database and choose a channel for run reports.
- 4Test using one real approved order and review the draft confirmation.
Questions about this workflow
Is the confirmation sent to the client?
The action creates a draft in Lexoffice. Review and deliver it through your established process.
Can I trigger this from an approval property?
Select the Notion Page Properties Updated trigger and describe the approval condition in the prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Lexoffice. A trigger fires from one place; an action lands in another.
Notion triggers
Lexoffice actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Article
Tool to create a new article (product or service) in Lexoffice. Use when you need to add items to the product/service catalog for invoicing or quotations. The leadingPrice field must be uppercase (NET or GROSS).
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create contact
Tool to create a new contact (customer or vendor) in Lexoffice. Use when you need to add a new business contact. Either company or person details must be provided, and at least one role (customer/vendor) must be assigned.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Credit Note
Tool to create a credit note in Lexoffice. Credit notes are created in draft mode by default; set finalize=true to create with status 'open'. Use when you need to issue a refund or credit for an invoice. Maximum 300 line items per credit note.
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 Delivery Note
Create a delivery note in lexoffice. Delivery notes are created in draft mode by default (set finalize=true for open status). Use when shipping goods or providing services and need to document what was delivered without prices/payment terms. Maximum 300 line items allowed per delivery note.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Event Subscription
Tool to register a new webhook for Lexoffice events. Use when you need to receive real-time notifications for specific events like invoice creation, contact changes, or payment updates.
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 Order Confirmation
Tool to create an Order Confirmation in Lexoffice/Lexware. Order confirmations are always created in draft mode and do not need to be finalized. Use when you need to confirm a customer order with line items, pricing, and shipping details.
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.
Create Quotation
Tool to create a quotation in Lexoffice. Quotations are created in draft mode by default. Use the finalize parameter to create a finalized quotation with status 'open'. Requires address with either contactId or name+countryCode, line items, total pricing, and tax conditions.
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.
Create Voucher
Tool to create a bookkeeping voucher in Lexoffice. Use when you need to create expense receipts, sales invoices, purchase invoices, or other accounting vouchers. The voucher requires line items with amounts, tax rates, and posting category IDs.
Connect any two apps with Notis in the middle.
Notion and Lexoffice, 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 Lexoffice.