Examples

Sentences you could say today, by shape. Every one starts from something Dustav can actually see: an email in your inbox (and the files attached to it), an email you send, a table those emails filled, your calendar, or the date. A website, a portal or an app counts only when it emails you — Dustav doesn't follow links or log in anywhere. Within your email, no predictable sender is needed: a rule that recognises a kind of email catches the vague note from a stranger as well as the order notification. Say one as-is, or say yours. The same list lives behind Create workflow on the Workflows tab, after Make your own — a tap opens a picture of what the workflow makes and hands it to Dustav.

Table — stop retyping it

• "Every inquiry that lands in my email — my website form's notification or a customer writing in: name, email, what they're after, and when they'd like it." — Recognised by kind, not by sender — a vague email from a stranger lands the same as a form's notification.
• "Every order email my online shop sends me: customer, item, quantity, total, date." — Matched by sender; the sealed reader pulls each column off the receipt.
• "Every invoice a supplier emails me: vendor, invoice number, date, amount, due date." — Recognised by kind; the reader opens the attached PDF and reads the amount from it, never from memory. A portal link isn't followed.
• "Every shipping email: carrier, tracking number, what's in it, and its status — one row per parcel that updates when it arrives." — Keyed on the tracking number — a number the source issues — so a later email finds its row.
• "The season schedule the league emails each spring: one row per session — date, time, location, team." — One email that is a list becomes one row per line.
• "Every registration email my booking form sends me: student, email, class, date, fee." — Matched by sender and a subject word; the roster becomes the source for reminders.
• "Every market or fair confirmation email: the event, the date, the booth fee, and whether we're accepted." — Recognised by kind — every organiser's email looks different and that's fine.
• "Every membership payment email: member, email, plan, amount, the month it covers." — Matched by sender; the money column totals when you ask.
• "Every rental receipt email: customer, date, and how many units — the count is the rental total divided by the unit price, not the quantity on the line." — A hint on the column tells the reader where the value hides or how to compute it — fixed once, not corrected weekly.
• "Every quote I email a customer: who it's for, what it covers, the amount, and the date I sent it." — Fires on your SENT mail: right after a quote goes out, the sealed reader pulls its columns. Older sent quotes can be backfilled.

Email — write it for me when it happens

• "When a customer emails a file that has to go to my supplier, draft the order to the supplier with their file attached." — A fixed recipient; the triggering email's own files ride the draft.
• "When someone emails about custom work, reply with our commissions overview — the same words every time." — Reply mode: the workflow says when, the template holds the words.
• "When the supplier emails that an order is ready, draft the pickup note to the customer from that thread." — The recipient is found by reading; an address that doesn't exist in your mail is refused.
• "When a new wholesale account emails, draft the welcome with the price list attached." — The template carries the price list as a linked document — replace the file once, every future draft follows.
• "When a supplier emails an invoice, draft the forward to my bookkeeper." — A fixed recipient plus the source files.
• "When a client emails the signed contract back, draft the kickoff email to them." — Back to the sender — no address to store, read off each email.
• "When I send a new member their welcome email, draft a second email to them with the discount code." — Fires on what you SEND and goes to whoever you sent it to. If the welcome comes from your own app or site, putting the code in it is simpler — Dustav will say so.
• "When I email a job over to a subcontractor, draft the heads-up to the customer it's for." — Fires on what you send; the customer is found by reading — an address that isn't already in your mail is refused.
• "When a parent emails about a birthday party, reply with the party info and the booking link." — Reply mode from a template.

Schedule — the day before, every monday

• "Every morning, anyone whose class is tomorrow gets the reminder; if they're bringing their own tools, attach the checklist." — A morning check against your table; the template's documents ride along; each class is drafted once, ever.
• "Every Monday, everyone on my party bookings table with a party this week gets the confirmation, waiver attached." — A weekly condition over a table your booking emails fill; the template carries the waiver.
• "Every morning, anyone on my memberships table whose renewal is three days out gets the renewal note." — A date condition over the table the membership payment emails fill.
• "Two days after every class, draft the post-class survey to that class's students from my registrations table." — A condition that looks backwards two days; the ledger keeps it to once per class.
• "Every Friday, draft me a list of the supplier invoices due next week." — A weekly condition over a table email fills; the recipient is you.
• "On the 1st of every month, draft the rent transfer note to the landlord." — No table at all: the condition is the date and the recipient is an address you gave.
• "Every morning, draft me a note with today's calendar." — The recipient is you; the condition reads the calendar window.

Follow-up — after i send something and hear nothing

• "Three days after I send a quote with no reply, draft a friendly nudge — twice at most." — Nothing is armed and nothing is cancelled: each morning Dustav checks whether the last message on the thread is still yours.
• "A week after I send the final invoice, if they haven't written back, draft the review request." — Silence on the thread is the only thing it claims — you see "no reply since you sent it" beside the draft before you send it.
• "Two weeks after I email an invoice with no reply, draft the friendly reminder — once more a week later, then stop." — It knows there's been no reply on the thread — never whether it's paid. A payment that came by e-transfer or cheque reads as silence, so you're the last check.
• "If someone I send a proposal or a plan to goes quiet for five days, draft a check-in." — Their reply, or you following up yourself, simply means nothing is due — there's nothing to cancel.

And a few that aren't workflows

• "Remember that Tuckahoe is our clay supplier and orders go to orders@tuckahoe.example." — a fact.
• "Keep our studio policies somewhere I can attach them." — a document.
• "This is the exact email we send when a piece is ready." — a template — then a workflow decides when.
• "Send this to her Thursday at 9." — Schedule send, on the draft's arrow.

Every one of the workflows above prepares; you send. Every row comes off a real email. If you're not sure which shape you're describing, just say the job — Dustav picks the shape and tells you which and why.