Give the next step a starting signal
A purchase lands. An issue opens. An email arrives. A job fails. Minion runs the package that handles it, whether or not anyone is chatting with an agent.
Four ways work starts
Schedules
A package declares a job with a cron schedule and a timezone. It runs on time, every time, with each run logged.
Webhooks
GitHub, Stripe, Slack or your own tools POST to a secret URL and a package runs. Minion hands out the URL; your agent never needs to see it.
Events
Packages can subscribe to things that happen in Minion, like a run or a job failing, or to topics other packages emit.
Mail arriving at your team inbox can start a package, so forwarding a message is enough to kick off the next step.
Know when something breaks
Every run recorded
Each run keeps its logs, result and error. Failed runs wait on a triage list until someone marks them resolved or ignored.
A note on what went wrong
When something fails, Minion writes a diagnosis note: the error, the last good run, and what changed since.
Later, or longer
Run something once at a set time, or as a background run with more time than an interactive call allows.
Let the work start on its own
Ask your agent to put one routine task on a schedule.