Guided Build settings
Bless program templates, set clone destination folder rules, and choose workflow gates for Guided Build on each Marketo connection.
Guided Build settings live under Settings → Agent context → Guided Build in the product (/settings/agents/campaign-strategist). They decide which Marketo programs Guided Build may clone from, where new programs land, and which approvals apply before anything is written.
/settings/agents/campaign-strategist).
/images/agent-studio/guided-build/settings-readiness.pngSettings, Agent context, Guided Build (/settings/agents/campaign-strategist) with a Marketo connection selected, Readiness section showing configured items and at least one blocker with its Fix this action. Use a demo instance.
| Section | What you configure |
|---|---|
| Readiness | Whether this connection is ready for Guided Build to clone programs. Lists blockers, warnings, and what is configured so far: blessed template library, clone destination folder rules, and token policy. |
| Template library | The Marketo programs Guided Build clones from. Add (bless) templates and test which template a program would get. |
| Clone destinations | Folder rules that decide where a new program is cloned, plus folders Guided Build must never use. |
| Token policy | Which program tokens Guided Build may write at clone time, which can remain as placeholder values, and which are populated automatically by a sync. |
| Workflow gates | Approval and template choice behavior applied before Guided Build writes to your MAP. |
- Add a template: search for an existing Marketo program by any part of its name, check what is inside it (emails, landing page, form, list), then choose Bless this program.
- Blessed templates are listed by workspace with their motion and dimensions. The list is read-only, and a daily sync keeps each template’s structure current.
- Try it: which template gets picked? Search a real program and add an optional brief snippet to see which blessed template wins and which other candidates were considered.
/images/agent-studio/guided-build/settings-template-library.pngGuided Build settings, Template library, showing blessed templates grouped by workspace and the Try it panel with a template pick result. Use a demo instance.
Search a Marketo folder by name, then check which of its subfolders should each get their own rule. Each folder rule has a destination folder, a path template, and optional When conditions (for example, only for one marketing team). A rule with no conditions applies to every program.
Use Preview a draft rule before saving with made-up values to see which rule would apply. Under Exclude folders, list path prefixes or folder name fragments Guided Build must never propose or clone into. Validate against a real program checks whether your rules would place a program like an existing one in the same folder. It is read-only.
Which tokens are writable at create time, which are placeholder-OK, and which are sync-populated. Tokens not marked writable are left untouched when the program is cloned.
| Setting | Options |
|---|---|
| Require plan approval before MAP writes | On by default. A plan must be approved in chat before Guided Build writes anything to Marketo. |
| Template ambiguity | Ask when multiple templates match (default) lets the marketer choose in chat. Auto-pick archetype default picks for them. |