Start from a template
You will build: a complete, working app scaffolded from the template catalog — the fastest route from idea to running pipeline when your use case is a known shape.
Prerequisites
- Pulse CLI (quickstart).
1 · Browse the catalog
pulse new --list-templates
220+ templates across industries — support, finance, marketing, ops, IoT… each one a complete multi-stage app.
2 · Materialize one
pulse new my-responder --from-template kb-grounded-ticket-responder
The template transpiles into a plain pulse.yaml in ./my-responder — not a black box: open it, read it, it's the same three blocks you know.
Other real examples to try: voice-customer-support-agent, ai-call-center, roas-influencer-campaign, ai-virtual-office.
3 · Fill in what's yours
The scaffold emits ${env:…} / ${secret:…} for every credential field — set them, then:
pulse deploy .
Templates using MCP plugins ship with a pack reference — the deploy wizard offers the plugins as a one-click install instead of a scavenger hunt.
4 · Make it yours
$EDITOR pulse.yaml
A template is a starting point, not a cage: add a stage, swap the sink, tighten a rule. From here it's a normal app.
What just happened
Templates compress the blank-page phase: a proven pipeline shape lands as an editable pulse.yaml, with secrets stubbed the right way and plugins bundled. You keep the golden path (edit → deploy → tail) from minute one.
Troubleshooting
A template stage shows blocked after deploy
It uses an MCP plugin you haven't installed yet — the pipeline view names it, the wizard offers the install. Same honest-blocked behavior as in Acting with MCP tools.