Automations

What an automation is

An automation is a repeatable flow that takes inputs, runs controlled steps, and generates an output that is useful for the business.

It can run manually, on a schedule, or from an event depending on the use case.

What it should include

A well-defined automation usually includes:

• Operational purpose.
• Configuration data.
• Execution parameters.
• Allowed inputs.
• Expected outputs.
• User-visible errors.
• Impact metrics.
• Billing model or usage limit.

Configuration vs execution

Configuration is saved and reused for future runs. Examples include recipients, language, time zone, frequency, or a list of operations.

Execution is a specific run. It may use saved configuration and additional parameters from that moment.

Timeline

The timeline shows the main steps of an execution. It should help the user answer:

• What started.
• What is running.
• What finished.
• What failed.
• Which business object was processed.
• Which output was generated.

Impact

Automations can register operating impact, such as time saved, operations processed, or errors avoided.

That impact should connect to a clear unit, not a generic metric.