automation_save

com.emdly/emdly · Verify this server

Create an automation for the hosted agent, or replace one (give its `id`). When the owner asks for it — a hosted agent also builds one when the owner asks for anything recurring (a regular report, a check on a schedule, handling of certain e-mails), or after they said yes to its offer. A trigger starts it — manual, schedule (every 15m/30m/1h/3h/6h/12h/1d/1w, at HH:MM, day mon–sun, Prague time) or mail (a connected mailbox, optional from/subject filters, attachments) — then `steps` run in list order unless `next` says otherwise (null ends). Each step: type "step" with a short `name` and `description` (what should happen, in plain words — the agent then does it with its skills and connections); type "condition" with `name` and a yes/no `question`, going on along `yes` / `no` (step ids or null); type "send" with an optional `message` (empty = the previous step's answer), posted where the agent writes on its own (the chat it was last talked to in) — to post into a particular channel, say so in a step instead ("post the summary to #ops"). Ids are yours (e.g. "save", "notify"). `enabled` switches it on (only when nothing is missing). Returns the id, the editor link and what is missing.