Routines
A routine is a standing instruction. You write it once, and it runs on a schedule. Every Monday, send me the churn report. Every weekday, summarise new support tickets. Routines run on Agently's servers, so they keep going while your computer is off.
The full guide, with every step and setting, is the help article Routines.
In short
- Create one from a sentence: choose New routine on the Routines screen and say what it should do. Jarvis recommends a schedule, a model, whether it checks for anything new first, an approval setting and a daily credit limit, with the cost. Change anything, then choose Create routine. You can also ask Jarvis in a chat.
- Quiet runs are skipped. A routine set to check first skips the run when nothing is new, and uses no credits for it.
- Approval. Ask before sending holds every outside change for you. Turned off, the routine runs unattended. Routines never delete anything.
- Plans. Routines need a paid plan. On the Free tier they are saved but stay paused.
- Credits. Runs use credits, or your workspace's own API key at no credits. See Credits and your own API key.
What routines are good for
The test is whether you would put it on a recurring calendar invite for a person.
- A digest. Monday morning summary of what moved last week, pulled from your connected tools.
- A sweep. Daily pass over new support tickets, sorted and assigned.
- A chase. Weekly look at unpaid invoices with a drafted follow-up for each.
- A watch. Competitor pages or a news query checked on a cadence, with anything new saved to your Brain.
Related pages
- Routines, the help article
- Approvals, what Jarvis asks before doing
- Integrations, the tools a routine reads and writes