Plan a simple workflow before automating it

Start with a process you can explain in a few sentences. Automating a vague rule makes the confusion repeat faster.

A trigger starts the workflow. A condition chooses a route. An action changes something or communicates it. An output is a value or result produced by a step.

Define your first process

1. Choose a small outcome. Start with a non-critical comparison or internal check, not a payment or an automatic customer message.

2. Define how it starts. A deliberate manual start is different from a recurring schedule or an external event. Choose the start the process actually needs.

3. Identify the inputs. Name each value, where it comes from and what it means. A value entered by you is not automatically connected to a live task or checklist.

4. Write the rule. For example, compare a reviewed-item count of 4 with a target of 5 using equals. The result is false because the two counts differ. That result is not a software error.

5. Define both outcomes. Decide what should happen when the condition is true and when it is false. If an outcome sends a message or changes a record, specify the destination and content instead of leaving them implied.

Find the workflow in Flow+

Open Flow+ → Workflows in the correct workroom. For an existing draft, read its name, description, trigger and current state before opening the builder. A name such as “Check reviewed items” does not prove that the workflow retrieves those items automatically.

Your result is a clear process you can build and test: known inputs, one understandable rule and deliberate effects. Saving a draft, running it once and allowing future starts are separate steps.

Before running anything: Read every action in the workflow. Do not start an unfamiliar automation just to discover what it changes.