Skip to main content

Elicitation and Approvals

Real workflows often need human input partway through execution.

That input might be:

  • approval for a risky action
  • a missing field or choice
  • confirmation before publication
  • clarification about how the workflow should continue

Worka treats that as a first-class workflow event rather than as an awkward interruption.

Two kinds of human interaction​

Think about two different cases:

Elicitation​

Use elicitation when the workflow needs more information from a person.

Approval​

Use approval when the workflow already knows what it wants to do but must not proceed without human consent.

These are different interactions and they should feel different in the product.

Do not bolt approvals onto the end of a build. Decide up front:

  • which steps need human input
  • which steps need human permission
  • what the workflow should do after the response arrives

That makes the workflow predictable rather than improvisational.