- Read the mail that came in overnight
- Search your files for the projects it mentions
- Sum up what needs you first
Kept in the runA morning note, kept in the run. Your mail is untouched.
Business · Customization · Automations
An automation is a saved workflow Vulcan runs with no chat open. A trigger starts it. Its steps run in order, and each step is recorded.
The times, senders and files are invented, so read this as what the triggers can do.
Kept in the runA morning note, kept in the run. Your mail is untouched.
Kept in the runA check note is written in the run’s own files. Nothing is sent.
Kept in the runA one-page brief, ready before the meeting. The event is not changed.
Kept in the runThe note sits in the run record.
Kept in the runThe summary stays in the run. Nothing is written back to the other system.
A timetable, Run now, another app calling it, a message arriving, or ahead of a calendar event. You choose one for each automation.
Once on a date, every few minutes, every day, or on the days you choose. The shortest gap is five minutes and the longest is a day. The time is read in the time zone you name.
Filter by sender, subject or words in the text. Each matching message starts one run. Sent mail and drafts never start a run.
Choose how long before: one minute to a day. Each matching event starts one run, and a cancelled event never does.
The automation gets a web address shown once, so another system can call it. Make a new address and the old one stops working at once.
It reads, searches and sums up. It writes its notes in the run’s own files. Document, deck and sheet tools and drafting mail are not available inside a run.
Some tools cannot run in an automation at all: sending mail, changing a shared calendar event, and anything that writes to another system.
A regular account keeps two automations and runs them ten times each month. Paused automations count, and the count starts again on the first of the month.