Created with AI.
A first workflow should be small enough to complete and useful enough to be used. This guide walks you through a simple notification workflow and the steps that will ensure it still works a year from now.
Start with a specific event, and add filters so that the flow only runs when relevant. A flow that runs whenever any change occurs results in thousands of empty runs.
Your first flow should have two or three steps. Send a notification or create a task. Flows with twenty steps are difficult to troubleshoot, and you will need to troubleshoot.
Trigger the flow manually and review each step in the run history. There, you can see exactly what went into and came out of each step.
Before the flow is put into operation, it must be owned by an account that will not disappear. This is the step most people skip, and the one that costs the most later.
Send the notification to a mailbox monitored by several people. A flow that fails silently is worse than no flow at all—people trust that something is happening.
Two sentences about its purpose and owner, somewhere others can find them. A year from now, this will be the difference between a flow that can be changed and one that no one dares touch.
Ask a question or share what helped you.

Published 2/12/2025
ProsessPilotene has developed a completely new solution for payroll deductions. TrekkSenter makes it easy for both trade unions and payroll departments to process deduction lists.
Read more
Published 10/7/2024
A portal solution is a smart investment for many businesses. It not only improves the customer experience and usability, but also offers the opportunity to significantly reduce costs through efficient self-service.
Read moreDo you have a question or experience to share?
Be the first to contribute.