{
"_id": "etp_A1B2C3D4E5F6G7H8I",
"name": "Follow-up after demo",
"subject": "Next steps",
"message": "<p>Hi {{firstName}},</p><p>Thanks for your time yesterday.</p>",
"cc": [],
"tags": [
"follow-up"
],
"createdBy": "usr_A1B2C3D4E5F6G7H8I",
"createdAt": "2026-09-01T10:00:00.000Z"
}Objects & Definitions
Message template
A message template is a whole reusable message — a subject and an HTML body —
saved by a member of your team from the Templates page (Templates > Emails) or
from any editor’s “Save as template”. The library is shared by the team, and a
template can be inserted as a step on any channel, as an inbox reply or as an
extension message: it carries no channel of its own.
Bodies are stored as HTML with
{{variables}} left raw, so a template reads
the same way it will be personalized at send time. subject, cc and tags
are always present in the API, empty when the template never set them.
Use List message templates
to browse the library with the Templates page filters (name search, tags,
creators), List message template tags
to discover the tags in use, and Get message template
to read one with its body.
Campaign step bodies are stored alongside the library but are not templates:
they are never listed here. Read a campaign’s steps with
Get campaign sequences.
A library message template: a whole reusable message a user saved from the Templates page or an editor, usable as a step on any channel. Bodies are HTML as stored, with {{variables}} left raw.
Template identifier (etp_)
Name shown on the Templates page
Subject line; "" when none was set
HTML body, variables left as {{variable}}
CC addresses; [] when none was set
Tags, trimmed and lowercased; [] when none was set
Creator user id (usr_), see GET /team/members
Creation date
Was this page helpful?