Processing and waiting time
Step durations distinguish processing time from the wait for parts to arrive.
Workflows
Set up the routine. Get on with your work.
Automations built from triggers, conditions and actions
A workflow starts when an event happens, checks the conditions you set, and carries out a series of actions. Send an invoice after an order is confirmed, email a customer when payment arrives, or create and assign a follow-up task when a colleague completes their work. Each run follows your rules, so routine work happens consistently without someone handling every step.
Define each step of a recurring process
A workflow defines what starts a process, what information it checks and what happens next. This maintenance example checks stock after a service request, orders missing parts, waits for delivery and prepares the technician’s work order.
The starting event
A new service request starts the workflow and checks the equipment and stock.
Actions determined by conditions
If a required part is missing, the workflow creates a purchase request.
Wait for the next event
Pause until the parts arrive, then continue with the next step.
Create the document your team needs
Generate a work order with the instructions the technician needs for the intervention.
See what each automation did
Execution history shows the steps a workflow followed, the information it used and what it created. Completed runs, steps waiting for an event and failures are visible together, so your team can identify what needs attention.
Review the purchase it created
Open the purchase request to check items, prices, and delivery status.
Understand why a condition was met
Check the stock levels that led the workflow to request more parts.
See the work added to your schedule
Find the scheduled intervention and the technician assigned to carry it out.
Monitor your workflows together
Run statuses distinguish completed workflows, waiting steps and failures needing attention.
Follow the records created by a workflow
Find the request, purchase, delivery, and work order from the same workflow run.
Include approval steps when a decision needs a person
Routine steps can run automatically while decisions wait for a person. For example, a purchase above your chosen amount can require a manager’s approval before the workflow continues.
Review the amount before approving
Check the purchase total and item costs before making an approval decision.
The person responsible for approval
Find the person responsible for approval and the time left to respond.
How teams automate recurring work
Use the same process each time, with clear steps and a visible record of what happened.
Set up the process once, then run it whenever needed
Automate customer follow-ups and internal handovers with triggers, conditions, and actions.
Questions about Workflows
A workflow can start when a business event occurs, such as a form submission, a received payment, or a task changing status. You choose the trigger, then define the conditions and actions that follow. For example, wait two days after a form submission before sending a follow-up email.
Automation tools that follow your working methods.
In a 30-minute demo, review your recurring tasks, triggers and approval points, then see how to translate your process into Eno workflows.