- 1. Install it and sign in
- 2. Have a real conversation
- 3. Connect an app with your own account
- 4. Let it act on real files
- 5. Put the job on a clock
- 6. Make the result visible
- 7. Package it as a role
- 8. Share it, or publish it
Step 5 of 8 · about 20 minutes
Put the job on a clock
Make something happen while you are not at the computer.
Do this
Open the Workflows panel and start a new one, or describe the whole thing in chat and let it wire the canvas.
Try this
Build me a workflow that runs every morning at 8, checks <the thing you want checked>, and sends me a notification with the result. Show me the steps before you save it.
plexon://panel/workflowspaste once installed
Choose Schedule as the trigger. Set it to every five minutes while you are testing.
Add one Tool step that calls a connector you already signed into. No AI needed.
Add a Notify step so you can tell it fired.
Save, then press Run now once before leaving it alone.
Change the schedule to something sensible once you have seen it work.
You are done when
A notification arrives on its own, and the run appears in the Runs tab with a timestamp you did not click.
What just happened
The engine is on your machine, not a server. Every run is snapshotted, so you can open one from last week and see what it saw. And it sends at most once: a retried run does not send the message twice, which is the failure that makes people switch automation off.