All field notes
AUTOMATION2 MIN READ

Automation should be easy to read.

A workflow can be quick to create and surprisingly hard to return to. The labels still look familiar, but the reasoning behind them has disappeared. Readability is part of the work.

Make the handoff visible.

The important action often happens between two boxes. A trigger produces a payload, a transformation changes its shape, and an action expects particular fields. When those handoffs are hidden, a diagram can look clear while the workflow itself remains difficult to explain.

Showing the input and output of each step gives the diagram something concrete to describe. Concrete JSON can reveal a missing field, an unexpected type, or an assumption that only existed in the original author’s head.

Name steps for their purpose.

“Transform data” tells us the kind of step. “Format the deployment message” tells us why it exists. Both are useful, but purpose deserves the more prominent label.

Names should remain specific enough to help the next person. A workflow that reads “Deployment received → Format notification → Send to engineering” carries more meaning than a row of provider logos.

Treat a failed step as useful information.

An error message can preserve the workflow’s readability. Tell the developer which step could not continue, which input caused the problem, and what that step expected. Retaining the last successful output makes investigation easier.

Automatic retries need the same care. A retry policy changes the behavior of the workflow. Its limits and delay should be visible, and actions that create side effects need deliberate handling of duplicate requests.

Keep the sequence legible.

A clear workflow makes the path from trigger to handoff easy to follow. Each step should explain its purpose, show the data it receives, and make its output available to the next step.

Readable automation depends on consistent boundaries. Keep names specific, transformations visible, and error handling close to the step it describes. Those habits help a workflow remain understandable as it grows.