Goal
Publish recurring digests faster while keeping formatting and handoff stable.
Run recurring content digests with repeatable structure so editorial teams and developers stay aligned.
Workflow assembly
Trigger to production output
01
Real send event
02
Message journey
03
Complete structure
04
Reusable blocks
05
Production output
Sent on a regular cadence for editorial and product content roundups.
Publish recurring digests faster while keeping formatting and handoff stable.
Editorial Newsletter System
This workflow is part of the Pro archive. Use it when this send is recurring enough that source ownership, QA notes, variants, and handoff context matter more than a one-off template.
Workflow pages expose the production shape before purchase: trigger, goal, required fields, variants, QA risks, handoff steps, and linked layout. The paid archive adds the editable source and compiled output for the workflows included in your tier.
A workflow is useful when the implementation contract is visible before anyone starts editing markup.
digest.issue_title
Edition title for this digest send.
digest.featured_article_url
Main article destination in the top block.
digest.secondary_items
Array of additional links for the roundup grid.

Editorial newsletter recipe combining an editor note, a lead feature, a roundup grid, and a lighter social footer.
Header Centred, Newsletter Editor Note, Editorial Newsletter Feature, Blog Roundup Grid, Footer Social Light
blog-digest.mjml
The value is not only the rendered email. It is knowing what has to be checked before the ESP takes over.
Template Hedgehog prepares the source, compiled output, preview, QA notes, and handoff context. Mailchimp, HubSpot, Salesforce, NetSuite, Klaviyo, Customer.io, or your ESP still handle audiences, consent, unsubscribe, automation, sending, delivery, and reporting.
Pro is the archive for teams that keep rebuilding production emails and need repeatable workflows, editable MJML, compiled HTML, QA notes, implementation guidance, and updates.