Set the process once.
A workflow specifies its trigger, inputs and steps. Code handles operations such as reading a source or saving a result. An AI step can summarise, classify or draft when the task needs judgement.
This makes the sequence inspectable. It does not make an AI answer certain or prevent an app from changing. Missing inputs, expired connections and failed steps still need handling.
| Part of the job | Useful approach | Example |
|---|---|---|
| Known operation | Programmed step | Read notes from a selected source |
| Interpretation | AI step with a clear input | Draft a concise follow-up |
| Commitment to someone else | Explicit review and tested permissions | Check a promise before sending |
Start with the work that keeps returning.
A good first workflow has a recurring trigger, a source you can access, and an output you can judge. Meeting briefs, follow-up drafts and recurring reports are useful candidates.
With awareness enabled, Jarvis can notice activity patterns. Your goals give those patterns business context. Treat a proposed routine as a starting point: confirm the actual steps and whether the work is worth automating.
Describe the result. Inspect the steps.
Describe one job
Name the trigger, source, output and actions that must stay off.
Review the draft workflow
Check its pieces, required connections, input mappings and error path. Composed flows start disabled.
Test with a small example
Run it with known inputs, then try a missing source. Inspect the output of each step.
Publish when it behaves as intended
Enable the trigger only after the test. Check run history and revisit the workflow when a connected service changes.
A prompt to start with
Create a draft-only workflow from meeting notes I supply. Extract agreed next steps, draft a follow-up and return it for my review. Flag missing owners or dates. Do not send email, change my calendar or publish the workflow.
Give the workflow the context it needs.
Memory can provide relevant company facts and preferences. Goals explain what you are trying to achieve. Connected tools, a browser or a desktop can provide the input and action surface.
Specify the context a step needs rather than assuming every saved fact will be retrieved. A hosted brain stays available independently of your laptop; actions on that laptop still require it to be awake and connected.
Build review into the job.
Use a draft-only first version when the result affects another person. If you later add a send or write step, configure its checkpoint and test the exact execution path. A review instruction in a prompt is not a substitute for an enforced checkpoint.
Authority settings govern agent actions. Piece-based workflows and connected services also have their own execution paths and credentials. Check their behaviour before you enable them.
By the Jarvis team · Reviewed