Intake from webhooks, polls, mentions and schedules

The idea

Work arrives from tracker webhooks (signed and deduplicated) or polls, and from @mentions of a worker. Cron schedules also open work, and a schedule can fire only when a watched event happened.

The problem
A person had to type work in, and the same issue could open twice.
Why it matters
All paths key on the issue and end up on one item, and a schedule skips when nothing changed.
Where it stands
In production as of

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

  • Automations from one sentence

    A message with timing words becomes a card (what, when, next three runs, who, credits); Start creates a schedule or event trigger whose runs report back to the asker.

  • Request rewrite

    When a worker first picks up an item, one structured model call rewrites the request into a working prompt and a short plan. The worker sees it next to the requester's exact words, and those words win.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.