openfolksRoutines and webhooks
A routine starts a fresh task once or on selected weekdays. A webhook starts the same kind of task when another system sends an HTTP request.
Routines
Each run starts a new task using that folk’s model, permissions, tools and computer. Run receipts record whether the work was queued, active, waiting, completed, missed, failed or cancelled.
Webhooks
Webhooks use a dedicated receiver on 127.0.0.1:8800 by default. It exposes a health route and secret hook routes only, not the rest of the OpenFolks API. Bearer authentication is preferred because the secret stays out of URLs and most access logs.
To accept events from the internet, proxy only the webhook receiver through a narrow relay or tunnel. Do not expose the main application port.
Limits
- Routines and webhooks run locally. OpenFolks must be running when a routine falls due, and closing the app stops the receiver.
Documentation
Next: Memory and voice