Approval workflows
Multi-stage approvals with delegation, escalation, and reminders - via Teams, Outlook, or in the app, with a traceable history.
Power Automate · cloud flows
Routine work takes care of itself. Reliably.
With Power Automate, approvals, notifications, document generation, and data synchronization run automatically in the background. I build cloud flows that work not only in testing but also in everyday use: with error handling, retries, logging, and clear responsibility.
- Cloud flows and desktop flows (RPA)
- PL-500 RPA Developer Associate
- 1,000+ connectors and custom APIs
01Use cases
What I use Power Automate for
Generate documents
Populate Word templates for quotes, reports, contracts, and certificates, generate PDFs, and store and send the documents.
Incoming emails and invoices
Identify attachments, extract data with AI Builder, store it, and send it to the right workflow.
Data synchronization between systems
Keep master data, orders, or documents in sync between SharePoint, Dataverse, ERP, accounting, and CRM.
Scheduled flows
Daily reports, deadline monitoring, follow-ups, and cleanup tasks - on time and without reminders.
Desktop flows (RPA)
Where there is no API, a desktop flow operates the legacy application like a human - selectively and as a bridge, not as a permanent solution.
02What I focus on
Quality you notice in everyday work.
Reliability
Flows that also run on a Friday evening
Many flows fail silently: an expired password, a locked file, an API limit. I build every flow with try/catch scopes, retry policies, meaningful error messages, and a log that shows what happened.
Connections use service accounts or, where the connector supports it, service identities - rather than the personal account of an individual who may eventually leave the company. Connection references make management and deployment easier.
- Error handling and notification
- Retries and timeouts
- Service accounts and connection references
- Logging and monitoring
AI in processes
AI where it really helps
With AI Builder and the AI actions in Power Automate, you can extract data from invoices and forms, classify emails, summarize texts, or suggest replies. I use AI selectively - with human review where decisions have consequences.
- Document processing
- Classification
- Summaries
- Humans decide
03Approach
From the first conversation to a solution in production.
Consulting and implementation from a single source: whoever writes the concept also builds it - with no friction between consultant and developer.
-
Initial consultation
Free and without obligation via Microsoft Teams: What is the challenge, what is the goal, and which licenses do you already have? Afterward, you will know whether and how the Power Platform fits your needs.
-
Process analysis
Together with the people who run the process every day: How does it work today, and where do manual handoffs between systems or media, delays, and errors occur?
-
Solution concept
Data model, screens, flows, permissions, and licensing - in writing, easy to understand, and with a clear effort estimate.
-
Implementation in stages
Short iterations, each with a working interim result. You see early on what is being built and can adjust course.
-
Rollout and handover
Acceptance, deployment to production, documentation, and handover to your team - so the solution does not depend on me.
-
Further development
If you wish, I will continue to support the solution afterward: enhancements, new requirements, and updates from Microsoft.
04Toolbox
Technologies in this area
- Cloud flows
- Approvals
- Desktop flows (RPA)
- AI Builder
- HTTP and REST
- Microsoft Graph
- Word templates
- Adaptive Cards
- Office Scripts
- Azure Key Vault
- Child flows
- Process mining
05Real-world projects
Projects in this area. No names, real substance.
As a rule, I do not name clients - their industry, size, and project requirements say enough.
Specialist retailer of fireplaces and stoves with delivery and installationsince 02/2022
Order processing for a stove retailer with Power Apps and SharePoint
For almost five years, I developed the central order processing system for a fireplace and stove retailer with several companies and locations, based on SharePoint, Power Automate, and Power Apps, and I still support it today. Quotes with digital signatures, invoices and payment reminders via sevDesk, Planner tasks, customer surveys with Forms, Power BI, and a mobile installation report on tablets all work together. The solution gave rise to the industry platform FLAMOX365.
more than 50 employees
SharePoint Online (lists and libraries)Power Automate (cloud flows)Power Automate approvalsPower Apps (canvas apps)Forms (customer surveys)
Read case study
Industry06/2026 - 09/2026
Order approval in manufacturing with Power Automate and SharePoint
For a manufacturing company, I implemented a multi-stage approval process for customer orders with Power Automate and SharePoint. Engineering, installation, order management, purchasing, and a second purchasing review handle approvals in sequence; rejections are routed back to the appropriate step with a required explanation. Nine flows, eight SharePoint lists, escalation, and an audit trail form the core system.
Part of a group of companies with more than 12,000 employees
Power Automate (cloud flows)Power Automate ApprovalsSharePoint Online (lists)Office 365 OutlookPower Platform solutions (managed and unmanaged)
Read case study
Energy and cable industry12/2025 - 09/2026
SharePoint migration, Power Apps, and Azure in the cable industry
For an international group in the energy and cable industry, I supported the migration of SharePoint and Power Platform applications. I developed the security and Azure architecture concept for a QHSE application and rebuilt three Power Apps for hazardous substance management, replacing an on-premises SharePoint solution with Nintex workflows.
more than 10,000 employees
Power Automate (cloud flows)Power Apps (canvas apps)SharePoint OnlineOn-premises SharePoint (source system)SharePoint REST API
Read case study
11/2021 - 12/2021Implementation
Shading systems
more than 300 employees · international sales
Rollout of Microsoft Power Automate as the central automation platform and automation of invoice processing with Microsoft Power Automate (cloud and desktop flows), Microsoft AI Builder, and Microsoft Dynamics 365 Business Central. In addition, real-time visualization of presence status via the Microsoft Graph API in SharePoint and Microsoft Power BI, as well as training on Dataverse and canvas apps.
- Power Automate (cloud flows, desktop flows)
- AI Builder
- Dynamics 365 Business Central
- Graph API
- Power BI (streaming dataset, REST API)
- SharePoint Online
- Dataverse
01/2021 - 04/2021Implementation
Financial services
more than 20 employees
Consulting, design, and technical implementation of landing pages with form data connected to the Microsoft Power Platform, as well as automation of pre-contract, contract, and signature processes with Microsoft Power Automate and Adobe Sign.
- Power Automate
- Adobe Sign
- WordPress
01/2019 - 03/2022Implementation
Distribution of ultra-fresh food
more than 4,500 employees · more than 2,500 locations in 7 countries
Building a central data foundation on Microsoft Dataverse and Dynamics 365, developing model-driven and canvas apps for location and quality management, and automating processes that affect revenue, such as multilingual online ordering and a delivery service, with Microsoft Power Automate, Web API, and Graph API. In addition, customer feedback with Customer Voice and Power BI, as well as training.
more than 200 automated flows - partially automated maintenance of data for more than 1,000 locations
- Dataverse
- Dynamics 365
- Power Automate (cloud flows, desktop flows)
- Power Apps (model-driven, canvas)
- Web API
- Graph API
- Power BI
- Customer Voice / Forms
- SharePoint Online
06Questions and answers
Frequently asked questions
What is the difference between cloud flows and desktop flows?
Cloud flows run in the Microsoft cloud and connect services through connectors and APIs - this is the standard approach. Desktop flows (RPA) control applications on a Windows computer through the user interface and are used when there is no API.
What happens if a flow fails?
I plan for errors: the flow retries when temporary issues occur, logs a clear description of the error, and notifies the responsible person or group - with a link to the failed run. This makes it easier to investigate and address detected errors quickly.
Can Power Automate work with systems outside Microsoft?
Yes. With standard and premium connectors, HTTP calls, and custom connectors, almost any system with a REST or SOAP API can be connected, for example ERP, accounting, CRM, or signature services.
Are there limits on the number of runs?
Yes, Microsoft limits the number of actions per day depending on the license. For flows with many records, I therefore plan batch processing, trigger filters, and lean loops - and check in advance which license is required.
Your process. My solution.
Tell me where things get stuck today - in a free, no-obligation initial consultation via Microsoft Teams, we will clarify what the Power Platform can do for your process and what a sensible first step looks like.