Templates in the dashboard

The dashboard’s Templates section shows every template your organization has pushed, renders the copy that will actually go out, and sends it to you so you can look at it in a real inbox. Nothing here edits a template: changing one is a cow push.

The list

One row per template key: the key, its tags, its latest version with when it was pushed, and the journeys that send it. Search filters on the key. Opening a row opens the template.

The template page

• Overview: the props the template declares, its send class, whether it asks for a verify link, the app that pushed it, and every journey that sends it.
• Preview: the latest version rendered with the example values from the props schema. Every prop is a field, so change one and render again to see that copy. This is the same renderer a send uses, in the same sandbox, so what you read is what a recipient reads.
• Send test: sends the message you are previewing to your own address, from an address on the domain your organization verified first. It goes to you and to nobody else: no consent is checked against a recipient, nothing is metered, and the row it leaves is a test. It shows under Recent sends on this page and on no one’s timeline.
• Versions: every version of the key, newest first, with its digest, when it was pushed, and whether it compiled.
• Source: the file as it was pushed.

Deleting

Delete is a row action and a last resort. It is refused while any journey still sends the template, and the message names them: delete those journeys first, or push a version that stops sending it. Deleting removes every version of the key.

The same from the CLI

cow templates list
cow templates get abandoned-checkout
cow templates preview abandoned-checkout --props '{"firstName":"Ada"}'
cow templates testSend abandoned-checkout --props '{"firstName":"Ada"}'
cow templates delete abandoned-checkout

The test goes to the address on your own account, never to one you name, so this is not a way to mail somebody. All of these need a signed-in session: a pipeline key does not reach templates.

Where next

• Email templates: the file contract, typed props, send classes, and verifyLink.
• Sending and delivery: the gates every send passes and what each status means.
• Your repo: how a push turns a file into the version this page shows.