Jobs
Scheduled actions created from chat or the dashboard.
A job is a prompt the agent runs on a schedule, with the same tools and connections as its owner. Jobs are personal or shared with the organisation, and every run's report lands in a saved chat.
Creating a job
From Chat. Ask for anything recurring:
every weekday at 9, check Help Scout for VIP conversations open for more than a day, look each customer up in HubSpot and the warehouse, and summarise the ones that need attention first
The assistant creates the job with memtro_schedule_job, confirms the schedule in words, and tells you when it first runs. It can also list, pause, resume, reschedule, run-now or delete jobs when you ask. See the worked examples.
From the dashboard. Dashboard → Jobs → New job. The form has schedule presets, a live description of the cron expression, timezone, scope, mode, model and memory setting.
Schedules
Five-field cron (minute hour day-of-month month day-of-week) in the job's timezone.
| Expression | Meaning |
|---|---|
0 9 * * 1-5 | weekdays at 09:00 |
0 * * * * | every hour |
30 17 * * 5 | Fridays at 17:30 |
0 9 1 * * | the first of each month at 09:00 |
*/15 * * * * | every fifteen minutes |
Jobs are checked every minute; a due job runs within that minute, up to ten minutes per run.
Scope and permissions
- Personal jobs are yours alone.
- Shared jobs are visible to the whole organisation and editable by their owner and organisation admins.
- Either way a job runs as the person who created it, with their connections and keys.
- Memory learned during runs follows the job's memory setting: shared jobs default to the organisation's memory, personal jobs to personal memory.
Results
Each run is recorded with its status, tool-call count, model and output, visible under the job on the Jobs page. The report is also appended to a saved chat named after the job, as a prompt and reply pair, so you can read the history in Chat and continue the conversation from a result. "Run now" queues a run outside the schedule.