How StoriBot reaches people when nobody is in the app, and how you send it work by email.
Mail from a job
Section titled “Mail from a job”A job writes to its receivers when it has something to say: a result the instruction asked for, a question it cannot answer, or a failure. The mail comes from StoriBot’s own address, as text with an HTML copy. Files the run made are attached, and if one of them is an HTML page it becomes the body of the mail.
If the mail went to someone other than the person who made the job, the footer says who that was, so a receiver knows whose job wrote to them.
Replying
Section titled “Replying”Reply to the mail. Your reply goes back into that run, and StoriBot carries on from it: an answer to its question, a correction, a follow-up. A question nobody answers is sent again after a day.
Emailing StoriBot a task
Section titled “Emailing StoriBot a task”You can start work by email, with no app open. Send the task to StoriBot’s address, shown under Settings, then Email. StoriBot runs it in your home organisation and replies with the result. The sender sees only what StoriBot writes back, so it tells you what it did before it ends.
Choose a home organisation once, under Settings, then Email: Make this my home organisation. If you have not chosen one, StoriBot replies asking you to, and does nothing else with the mail.
A task sent by email runs unattended, like a job. It cannot connect a system, change the Library, share a Stori or make a job, because nobody is there to say yes.
Email as an output
Section titled “Email as an output”A Stori can make an email: the update that goes to the team each week, or the client note, drafted from your systems and in your voice as a single HTML message. Sending it on a schedule is a job whose receivers are the people who should get it.