Connect GitHub to Lexoffice

When something happens in GitHub, Notis takes the next step in Lexoffice. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from GitHub to Lexoffice

View example

Bookkeep completed client work from merged pull requests

Create a bookkeeping voucher when a client deliverable pull request is closed and merged.

View example

Draft support quotations when GitHub releases change

Create a quotation draft for a release-related support package when release details are updated.

View example

Create client contacts from sales-ready GitHub issues

Create a Lexoffice customer contact when a new issue represents a qualified client request.

View example

Create order confirmations when project issues are approved

Draft a Lexoffice order confirmation when an existing project issue is marked approved.

View example

Create delivery notes after client pull request approval

Prepare a delivery note when a client-facing pull request receives an approval review.

View example

Draft launch-service quotations from GitHub deployments

Create a quotation draft when a production deployment signals a billable launch service.

View example

Create service catalog articles for new GitHub versions

Add a Lexoffice service article when a new version tag represents a sellable upgrade.

View example

Record shipped hardware assets from GitHub releases

Create a bookkeeping voucher when a release asset represents a shipped client hardware expense.

View example

Draft quotations for labeled client change requests

Create a Lexoffice quotation draft when an issue receives a client change-request label.

Supported Triggers and Actions

Notis builds workflows that link GitHub to Lexoffice. A trigger fires from one place; an action lands in another.

GitHub triggers

Lexoffice actions

New Workflow Artifact Created

Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.

TriggerPolling

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).

ActionInstant

Branch Changed

Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.

TriggerPolling

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.

ActionInstant

New Branch Created

Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.

TriggerPolling

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.

ActionInstant

Check Run Status / Conclusion Changed

Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.

TriggerPolling

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.

ActionInstant

Check Suite Status / Conclusion Changed

Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.

TriggerPolling

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.

ActionInstant

New Code Scanning Alert Created

Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.

TriggerPolling

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.

ActionInstant

New Repository Collaborator Added

Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.

TriggerPolling

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.

ActionInstant

Commit Event

Triggered when a new commit is pushed to a repository.

TriggerInstant

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.

ActionInstant

Trigger Types

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.

New Notion pageStripe chargeCalendar event

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.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

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.

Row insertedValue > limitQuery match

Why AI automation

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.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

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:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

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.