Triggering Workflows

A workflow should not feel like a hidden side effect.

Whether a workflow starts because of a user action, an incoming webhook, a tool result, or a scheduled event, the trigger should be understandable and reviewable later.

Common trigger types

Typical workflow triggers include:

• a user asks Worka to do something
• a view action starts a process
• an external event arrives through a service or webhook
• a previous step or hook adds follow-up work

What a good trigger definition does

A good trigger definition makes it clear:

• what starts the workflow
• what context is passed in
• which AI team member receives the first step
• what approval or gating applies before work expands

If those details are implicit, debugging the workflow later becomes much harder.