What is inside a blueprint
A blueprint is a set of components plus the settings they need. The components can be a folder, collections, stages and pipelines, saved filters, email templates, and automations, already connected to each other. The settings are values you choose at install, such as names and limits, and references to things that must already exist, such as a mailbox.
A blueprint is a set of components plus the settings they need. The components can be a folder, collections, stages and pipelines, saved filters, email templates, and automations, already connected to each other. The settings are values you choose at install, such as names and limits, and references to things that must already exist, such as a mailbox.
Requirements
None to read. To install one: a role that can create collections and automations. For what blueprints are for, see What a blueprint is.
Components
| Component | What it adds |
|---|---|
| Folder | A folder that groups everything the blueprint creates. |
| Collections | With their fields, some of them protected. |
| Stages and pipelines | A stage set and a default pipeline for a collection. |
| Saved filters | A starting filter, such as "all recipients". |
| Email templates | Ready-to-edit messages that its automations send. |
| Automations | Wired to the blueprint's collections and templates, sometimes one calling another. |
The Email Marketing blueprint, for example, installs nine components: a folder, Campaigns and Recipients collections, a starting audience filter, three templates, and two automations, one that dispatches a campaign and one that sends the sequence to each recipient. Available blueprints lists both blueprints in detail.
Settings
- Values: a name used as a prefix for everything created, a variant, operational limits such as daily sending caps. Each has a default or an example.
- References: things the components connect to, which must exist before install, such as the mailbox to send from or the collection that holds your audience. A reference can require something of its target: an audience collection must have an email group field.
What happens at install
- Conflict check. Sonta compares what the blueprint would create with what already exists, without changing anything.
- Per-component choices. For each collision: use the existing one, create alongside it with a suffix, rename the new one, or skip that component.
- All or nothing. Everything is created together, or nothing is, and a summary lists what was created.
The steps are in Install a blueprint.
After install
- It is ordinary configuration. Every component can be adjusted like one you built yourself; see Adapt a blueprint to your business.
- Protected fields stay. Fields the blueprint's automations rely on can be renamed but not archived.
- Installing again with the same name creates a second set with a numbered suffix, rather than overwriting the first.
- Removing the installation archives every component it created, in one step.
Notes and limitations
- Choices such as the CRM variant cannot be changed after install.
- Limits a blueprint sets can apply across everything the install runs, such as sending caps shared by all campaigns.