@workflowsdk's Hook primitive lets external events control a running workflow.
Let's take the email drip sequence example - welcome email, then nudges at day 2 and day 4. But what if the user completes the action before the nudges fire? You don't want to keep nagging them.
The pattern you can use to solve this: Define a hook, then race it against each sleep.
If the hook fires first, skip the remaining nudges. Any service in your app can resume the hook - it just needs the user's email as the token.