Glossary
Workflow Orchestration
Workflow orchestration coordinates a sequence of steps across systems, handling order, dependencies, retries and failures, so a process that spans several tools behaves as one thing rather than several.
Glossary
Workflow orchestration coordinates a sequence of steps across systems, handling order, dependencies, retries and failures, so a process that spans several tools behaves as one thing rather than several.
Step three should not run if step two failed; a step that times out should be retried a few times and then escalate; and the whole run should be visible rather than inferred from side effects.

A webhook starting an action is automation; knowing that the action is the second of five, that the third depends on it, and that the run as a whole either completed or did not, is orchestration.
If the honest answer is 'somebody notices eventually and re-runs it by hand', the process has outgrown simple triggers.
When a process has several steps that can fail independently and a partial failure currently means someone notices later and re-runs it by hand. That is the point where visibility and retry logic stop being optional.
Overlapping but not identical. Integration moves data between systems; orchestration governs the order, dependencies and failure behaviour of a multi-step process that may use those integrations.
Workflow orchestration coordinates a sequence of steps across systems, handling order, dependencies, retries and failures, so a process that spans several tools behaves as one thing rather than several.