Render Template
mandrill.render_template
ActionEmailconnection required
Calls the Mandrill API with the connection's credentials.
Render a template with content and merge values injected, without sending anything.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Mandrill
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- base_url, from_email, from_name, subaccount, ip_pool
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
template_name Immutable name (slug) of the template to render. | string | Yes | — | — | welcome-email |
template_content Content for the template's mc:edit regions, as an array of {"name": "region", "content": "<p>…</p>"}. Send an empty array when the template needs no injection. | array | No | — | array of object | — |
merge_vars Merge values to inject, as {name: content}. Mandrill's array of name/content pairs is accepted too. | object | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"template_name": "welcome-email"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
html The rendered HTML. | string | — |
{
"html": ""
}Notes
- Rendering uses the published copy of the template, not the draft.
See Render Template run in a workflow.
In a technical demo we add the Mandrill connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.