Integrations

Your systems. Our orchestrator.

Search the first-class connectors, select the systems you already run — and see in your system landscape which process templates Uhrwerk can connect today.

34
First-class connectors
11
Supported protocols
154
Agentic tools
37
Document types

1 · ERP

Choose your systems — and see your value immediately

Start with your ERP. We suggest companion systems and show which use cases apply today — and where a connection still follows.

Which ERP do you run?

ERP

Your system landscape

Select at least two systems so matching use cases can light up.

Process templates

Select systems — matching templates move to the front.

Process	Kind	Coverage	Status
ERP assistant Easier access to your ERP right away — search, explain, prepare, approve. Example“Show open PRs for plant DE-02” — ERP only, search + explain.	Single system	0/1	Still needed: ERP
Inbox control Classify mail, extract fields and attachments — without a second system. ExampleClassify inbound mail (order / invoice / master data) without ERP.	Single system	0/1	Still needed: Email
File adaptor / DMS Make PDFs and files usable via the file adaptor — basis for BANF and quotes. ExampleUpload PDF → detect type → stage for BANF/quote.	Single system	0/1	Still needed: DMS / Files
BANF process PDF → quotes via file adaptor, PDF and XC-Docs — controlled purchase requisitions. ExampleSupplier PDF with prices → file adaptor → XC-Docs → PR/quote in ERP.	System chain	0/2	Still needed: DMS / Files · ERP
Email → Order Order emails become controlled ERP sales/purchase orders. Example“Please ship 500× K-1042” → sales order in ERP.	System chain	0/2	Still needed: Email · ERP
Email → Accounting Invoice and booking-relevant mail lands checked in finance/ERP. ExampleIncoming invoice PDF in attachment → match vendor → post in finance/ERP.	System chain	0/2	Still needed: Email · ERP
Email → Master data Change requests from the inbox become clean master-data updates. Example“New ship-to from April” → update customer master in ERP.	System chain	0/2	Still needed: Email · ERP
Email → Article updates Article and material changes from mail are taken into ERP under control. ExamplePrice list / material change by mail → article master (price, text, status) in ERP.	System chain	0/2	Still needed: Email · ERP
ERP → Document ERP data becomes quotes, documentation and reporting. ExampleOpen order in ERP → generate quote PDF and store in DMS.	System chain	0/2	Still needed: ERP · DMS / Files
ERP → Email Status, confirmations and notices from ERP go out as targeted mail. ExampleDelivery-date change in ERP → customer info mail with approval.	System chain	0/2	Still needed: ERP · Email
Email → ERP → Email Answer inbox questions with internal ERP knowledge and write back. Example“Where is order SO-4521?” → query ERP → reply with status/document.	System chain	0/2	Still needed: Email · ERP

Workflow engine & holistic integration

Uhrwerk turns intent into approved system actions: signals from email, DMS or CRM are reconciled with ERP master data, orchestrated by the workflow engine, and executed with audit, approvals and cost limits — expandable as soon as another system joins.

Expandable by design

First-class connectors cover the core. Protocols (OpenAPI, OData, REST, GraphQL, SQL, FTP) and self-service adapters keep the stack open — without a big bang.

Talk about your landscape

First-class connectors at a glance

SAP S/4HANA(ERP)
SAP Business One(ERP)
oxaion(ERP)
Dynamics 365 Business Central(ERP)
Albatross(ERP)
Salesforce(CRM)
HubSpot(CRM)
Pipedrive(CRM)
HR4YOU(CRM, ERP)
Microsoft Exchange(Email)
Gmail(Email)
Google Drive(DMS)
OneDrive(DMS)
SharePoint(DMS)
M-Files(DMS)
XC-Docs(DMS)
Microsoft Teams(Office)
Microsoft Excel(Office)
Microsoft OneNote(Office)
Confluence(Office)
Notion(Office)
Asana(Office)
monday.com(Office)
Jira(Office)
Google Calendar(Office)
Lexware(Finance)
Power BI(Analytics)
GitHub(Other)
Canva(Other)
OData(Protocols)
OpenAPI V3(Protocols)
Swagger(Protocols)
REST(Protocols)
GraphQL(Protocols)
SQL(Protocols)
FTP(Protocols)