---
title: "Flows in ERPoida: automate the steps someone does every week"
description: "A flow is a trigger and a few steps that run the same way every time, with a log of every run. Here is how to build one by describing it, test it on one record before switching it on, and which ones small teams start with."
url: https://erpoida.com/blog/erpoida-flows-15-automations/
language: en
published: 2026-11-20T23:00:00.000Z
updated: 2026-11-21T00:54:25.809Z
author: "ERPoida team"
category: "Operations"
tags: ["automations","flows","workflows","operations","how-to"]
publisher: "ERPoida (DEVOIDA, LLC)"
translation_de: https://erpoida.com/de/blog/erpoida-flows-15-automationen/
translation_ar: https://erpoida.com/ar/blog/ar-erpoida-flows-15-automations/
---

# Flows in ERPoida: automate the steps someone does every week

> A flow is a trigger and a few steps that run the same way every time, with a log of every run. Here is how to build one by describing it, test it on one record before switching it on, and which ones small teams start with.

A deal is won, so someone creates the project. An invoice goes overdue, so someone writes the reminder. It's Friday, so someone checks who forgot their timesheet. Each step is small, they happen every week, and they're exactly what gets dropped when the week is busy.

A **flow** does them for you. It has a **trigger** (a record is created, updated or deleted; a schedule; a manual start) and **steps**: create or update records, ask a manager to approve, run an AI step, notify someone, add a comment, or send an email through a connected mailbox. Every run is logged with what each step did.

## Building one by describing it

Take the most common one: *when a deal is won, create an invoice draft and a kickoff project, and tell the account manager.*

You don't drag boxes. You tell the assistant that sentence. It picks the trigger (deal updated, stage becomes Won), adds the three steps, and fills in the fields: the invoice draft gets the deal's customer and amount, the project gets the deal's name, the notification goes to the deal owner.

Before saving, it validates the flow and tells you what's wrong, if anything: a required field it couldn't fill, a step that refers to something the trigger doesn't provide. You can also open the builder and change steps by hand; it's the same flow either way.

## Test it on one record before switching it on

This is the step people skip, and the one that saves the most trouble.

![Dry-run log of a flow, and the assistant explaining a failed run](/blog/media/91323ae3-761f-4375-b714-a963839fbea9)

"Run this flow now on the Acme deal as a dry run." A dry run walks through every step and shows what it *would* do, without creating anything. You read the log: invoice draft for Acme, €12,400; project *Acme website relaunch*; notification to Lena. If that's right, run it for real once, check the records it made, then enable it.

From then on, when it does something unexpected, "Why did the won-deal flow fail last night?" reads the run log and points to the step that failed and the reason.

## What small teams start with

**Sales**
- When a deal is won, create the invoice draft and kickoff project (above).
- When a deal is lost, ask the owner for the reason in a comment, so loss reasons can be reviewed later.
- Every morning, notify owners of deals nobody touched in 14 days.

**Finance**
- Every morning, notify invoice owners about [overdue invoices](/blog/invoicing-draft-post-get-paid/).
- When an invoice over €10,000 is created, require a manager's approval before it can be posted.
- Every month, create invoices for installments that are due.

**Projects and time**
- Every Friday at 16:00, remind people who logged fewer than 35 hours ([why time on tasks matters](/blog/time-tracking-with-ai/)).
- When a timer has run for more than 10 hours, tell its owner.
- When a project reaches 80% of its hour budget, notify the project manager.

**Operations and support**
- Every night, create draft purchase orders for products below their reorder point.
- When a ticket is created, classify it with an AI step and assign it to the right team.
- When an employee is created, generate their onboarding tasks for the manager.

## One at a time

Start with the flow that removes a task someone does every single week. Watch its runs for a week. Add the next one when the first runs cleanly. Ten flows nobody trusts are worth less than two that everyone forgets exist because they just work.

---
Run your business on ERPoida: https://erpoida.com/
