About
Manage the reusable message templates your workflows and outreach use — create and edit EMAIL/SMS/NOTE templates (with{{merge_fields}}) and
organize them into folders.
All operations go through the developer API gateway — one endpoint, called by
operationId. If you haven’t set up a key yet, start with the
Developer API Overview.
Operations
Reading templates (READ scope)
Writing templates (WRITE scope)
Dynamic variables use the same merge-field syntax as the app’s template
editor — see Content Templates for
the available fields and how they resolve at send time. Email templates may
store merge tags in both subject and body. Check that
renderContentTemplate returns an
empty missingVariables array before using a rendered message; sending
itself happens in the app.Organization guardTemplate and folder operations are org-guarded on the ids you pass — a template
id or folder id from another organization returns
403 forbidden. Listing and
creating happen under your own org. See
Authorization for the model.