Agent-readable docs index: /docs/llms.txt. Full docs in one file: /docs/llms-full.txt. Download /docs/docs.zip to grep all markdown files locally.

Create templates and personalize messages

Templates keep reusable message content consistent. Convert renders the saved design for a contact or API request and translates supported content for the selected provider. Template identifiers are public IDs such as tpl_..., not a provider's internal component name.

Prepare a template

Choose the channel and purpose, write the content, and add the variables the customer-facing message needs. Email templates can store subject, preview text, From name, and Reply-To information. Review both the message design and the sender setup before sending.
Meta templates need approval where the provider requires it. Convert displays the caller-facing values your application must supply and constructs provider-specific components, including authentication copy-code button parameters, internally.

Supply API variables

Use template and variables instead of a raw message. A request without channel still defaults to phone-based Smart routing; select email explicitly for an email template.
{ "to": "+2348012345678", "template": "tpl_your_template_id", "channel": "whatsapp", "purpose": "otp", "variables": {"otp": "638492"}, "test": true }
Missing required variables return 422 with error_code: "missing_variables" and a missing array. A template from another workspace is unavailable, and an archived template cannot be sent.

Distinguish temporary variables from profiles

variables are send-time values. Store persistent profile information deliberately in custom_fields; do not assume every variable is written to the contact. In particular, one-time verification codes should not become reusable customer profile attributes.
Preview real substitutions. Check a recipient with complete data and one with missing optional data, so greetings, links, and order references remain readable.

Use templates in automations

Each message action has one content source: select a template or custom content. When a template is selected, its preview replaces the custom subject/body editor. Publishing copies selected content into the immutable workflow version.
Next: send through the API, build a campaign, or configure automation actions.
Template edits do not rewrite running journeys. Existing executions retain the content snapshot from the published version they entered.