Reviewing the emails a workflow sends

When a workflow sends email, the step is email.draftCampaign — and Wally writes the real email into it, not a placeholder. Open the step in the editor and the panel "The email this sends" shows exactly what a customer receives, so a human reads the copy before anything goes out.

What you see:
• Subject and preheader — the two lines that decide whether the email gets opened. Both editable.
• Campaign name — an internal label only; recipients never see it.
• The body, block by block, in the order it renders: header, text, buttons, images, columns. Every text field and every link is editable inline.
• Layout knobs (alignment, size, tone, "hide if empty") are shown read-only — change those in the campaign composer after the workflow creates the draft.

Placeholders:
Copy often contains ${trigger.doc.customerName} or ${trigger.doc.tripName}. Those are filled in per recipient when the workflow runs. The panel lists every placeholder the email uses so you can confirm the data actually exists on the record that triggers the workflow.

Images you supply:
An image slot with no URL is deliberate — Wally never invents an image address, because a made-up URL renders as a broken image in the inbox. The slot shows as "An image goes here" with the alt text or caption describing what belongs there. Paste a URL into the slot to drop the picture in. The panel counts how many images are still waiting.

Sequences:
For a drip — an email, a wait, another email — each email step is labelled "Email 2 of 5" along with how long after the previous one it goes out ("3 days after email 1"), read off the workflow.sleep steps in between. That lets you judge the cadence and the copy together. Change the pacing by editing the sleep step's seconds.

Nothing sends while you are reviewing. The draft lives in the editor until you click Save, and Wally's drafts start disabled — you enable the workflow when the copy reads the way you want it to.