Expertise

    Power Automate for organisations in Lucerne.

    We support your Power Automate project from Bern and Sachseln. We agree with your team how to organise workshops, delivery and collaboration in Lucerne. Our first conversation focuses on your existing environment and the task you need to solve.

    01

    Event or schedule

    A new list item starts an approval, an incoming email creates a task, every night a flow syncs data with the ERP. When a step needs judgement, such as classifying a request, an agent takes it on and calls the flow as a tool. We look at frequency, volume and exceptions; for long-running transactions or high-load integrations, we assess Azure Logic Apps or a dedicated interface.

    02

    Cloud flows, desktop flows, agent flows

    We define triggers, conditions, actions and owners. Connections run through agreed service identities, and retries, notifications and logs are set up so that a failure is noticed and can be resolved. The building blocks:

    • Cloud flowsApprovals in Teams and Outlook, notifications, filing and data sync between Microsoft 365 and connected systems.Result: the next step starts as soon as the previous one is done.
    • Desktop flowsAutomation of applications without an interface, attended at the workstation or unattended on a dedicated machine.Result: older business applications become part of the workflow too.
    • Agent flowsWorkflows in Copilot Studio that an agent calls as a tool, or that read documents and draft replies with AI actions.Result: the agent acts by fixed rules, and every run can be traced.
    • ERP syncAbacus and bexio through the connections from the ERP integration, with sync of master data and documents.Result: every value is maintained in one place and is current wherever it is needed.
    • OperationsFlows in solutions, service accounts with limited rights, failure alerts to a named contact, analysis of runs.Result: a failure is noticed before anyone in the business runs into it.
    03

    Licences, accounts, cover

    Flows with standard connectors run with Microsoft 365. Premium connectors, desktop flows and flows in managed environments need Power Automate Premium or a per-flow plan; agent flows consume Copilot Studio capacity. The starting point is a business description of the workflow and access to the source and destination systems; we check API limits and data policies. An automated approval needs a rule for absence and escalation.

    04

    What happens on failure

    We test duplicate triggers, missing data, expired connections and recovery after a failure. Your team checks that a transaction makes only the intended changes. A person is named for changes; Support & Operations can take over day-to-day operations.

    05

    Arrange collaboration around the project

    Our offices are in Bern and Sachseln. Remote work and on-site meetings are arranged according to project needs. We clarify participants, working language, access and any travel effort beforehand. The location describes the service area, not an additional CNEXT office.

    Sound familiar? Tell us where you stand today.

    Contact in Lucerne

    Agree on a useful next step

    Tell us about your current workflow, the systems involved and the result you need. In our first conversation, we identify what else we need to know to plan a useful next step.