Templates
Reusable message and document templates for email, PDF, SMS, and WhatsApp.
EzFlow has two distinct template concepts. Understanding the difference helps you decide which one to reach for.
Communication and document templates
A communication template is a reusable piece of content you build in a dedicated editor and save under Templates (app route /templates). You write the message or document body once — with {{variable}} placeholders for dynamic data — and then fill those placeholders at Workflow run time using a TEMPLATE_FILLER node.
There are four channel types, one editor per type:
| Type | Editor route | TEMPLATE_FILLER node | Delivery node |
|---|---|---|---|
| Email / HTML | /html-template-creator/<id> | TEMPLATE_FILLER | SEND_MAIL |
/pdf-template-creator/<id> | — | PDF_GENERATOR | |
| SMS | /sms-template-creator/<id> | SMS_TEMPLATE_FILLER | SEND_SMS |
/whatsapp-template-creator/<id> | WHATSAPP_TEMPLATE_FILLER | SEND_WHATSAPP |
All four types share the same {{variable}} syntax. The backend extracts placeholder names from the saved template content so the filler nodes know which values to inject.
Template Library
The Template Library (app route /template-library) is a starter-template gallery. It contains two kinds of items:
- Document templates — pre-built email, PDF, SMS, or WhatsApp templates you can clone directly into your workspace and start editing.
- Workflow templates — complete automation Workflows that you can clone as a ready-to-run starting point.
When you clone an item from the library, EzFlow copies it into your tenant. A cloned document template appears in your Templates list; a cloned Workflow appears in your Workflows list.
A Workflow becomes a library template when its author marks it as isTemplate = true and isPublished = true. Both flags must be set for a Workflow to appear in the gallery.
How they relate
Communication templates and the Template Library serve different needs:
| Communication templates | Template Library | |
|---|---|---|
| What you build | A single reusable message or document | A browsable catalog of starters |
| Who creates them | You, for your own Workflows | Published by EzFlow or workspace admins |
| Used by | TEMPLATE_FILLER nodes inside Workflows | Cloned once, then used or edited freely |
| Runtime behavior | Filled with live data at run time | Cloned at setup time, not at run time |