Workflow automation

Anatomy of a workflow

Trigger

The event that starts it: a webhook, a schedule, a record change.

Conditions

The rules that decide which path runs. Every condition is a decision somebody must have agreed.

Actions

What it does: create, update, notify, route, transform.

Error path

What happens when a step fails. A workflow without one is a silent data-loss machine.

Observability

Run logs and alerts a human actually sees, including alerts on unexpected silence.

The properties that separate durable from fragile

• Idempotent. Re-running on the same input cannot create a second record.
• Observable. Failure and unexpected silence both alert someone within a day.
• Owned. A named person maintains it and reviews it on a schedule.
• Reversible. Mistakes can be undone without an engineer and a database.

What it is not

Workflow automation is not integration, though it often performs integration. It is not artificial intelligence, though a step inside it may call a model. And it is not a substitute for a decision nobody has made: encoding an unagreed rule simply moves the argument into a builder where fewer people can see it.

Score a candidate process with the automation readiness score before building anything.