Pull Template

Pull templates and all their variants from a SuprSend workspace into your local directory. Each template - including all its channel content, variant definitions, conditions, and mock data - is written to a local file that you can edit and push back. This action does not delete existing local files. Templates with the same slug are overwritten; new slugs are created as new files. By default, templates are saved to ./suprsend/templates/. Use --dir to change this. Specifying a directory is recommended when working across multiple workspaces.

Syntax

suprsend template pull [flags]

Flags

Flag	Description	Default
`-h, --help`	Show help for the command	–
`-g, --slug string`	Pull a single template by slug. Omit to pull all templates.	–
`-m, --mode string`	Version to pull: `live` or `draft`	`live`
`-d, --dir string`	Output directory for pulled template files	`./suprsend/templates`
`-f, --force`	Use the default directory without prompting for confirmation	–

Example

# Pull all live templates to the default directory
suprsend template pull

# Pull a single template by slug
suprsend template pull --slug order-shipped

# Pull all templates into a custom directory
suprsend template pull --dir ./my-templates

# Pull draft templates from production without a confirmation prompt
suprsend template pull --mode draft --workspace production --force

# Pull a specific template from production into a custom directory
suprsend template pull --slug order-shipped --workspace production --dir ./prod-templates

After pulling, the local files serve as your source of truth for editing. Make changes to variant content, conditions, or mock data, then run suprsend template push to upload the changes as a draft, and suprsend template commit to make them live.

Getting Started with CLI

Updates and Versioning

Sync

Workflow

Template

Schema

Event

Preference Category

Translation

Syntax

Flags

Example

​Syntax

​Flags

​Example

Syntax

Flags

Example