Workflow Templates

Templates give you a working workflow out of the box. Pick one that matches your use case, connect your integrations and customize the logic. Ship in hours, not days.

What’s in a template

Each template is a pre-built workflow with:

Blocks already wired up - the common pattern is modeled for you
Input and output schemas - fields are named and typed
Placeholder prompts - swap in your actual instructions
Integration hooks - connection points for your data sources and destinations

When you click Use Template, Scout creates a private copy in your workspace. The original template stays unchanged and your copy is yours to edit freely.

When to use a template

Use a template when:

You need a working baseline fast
The pattern is familiar (research, routing, summarization, enrichment)
You want proven block structure before customizing

Build from scratch when the process is highly custom or compliance-heavy.

Common template categories

Category	What it does	Common inputs
Research & summarization	Pulls sources, summarizes and formats output	Topic, URL or document
Support ticket routing	Classifies tickets and routes to the right queue	Ticket text, customer ID
Data enrichment	Looks up contact or company data and appends fields	Email or domain
Meeting follow-up	Transcribes, extracts action items and sends a summary	Recording or transcript
Lead qualification	Scores leads and triggers next steps based on criteria	Form submission data

How to use a template

Open Workflows
Click Browse Templates
Pick a template based on your objective and input data
Review the required integrations and data dependencies
Click Use Template
Update names, variables and destination systems
Run test cases in Console before going live

Before you go live

Check these before you deploy to production:

Replace all placeholder prompts and URLs with your actual content
Connect the required integrations in your workspace
Confirm environment variables are set in the right environment
Add error handling blocks for failure paths
Verify the output schema matches what downstream consumers expect

Use with agents

If an agent will call the templated workflow as a tool:

Use descriptive input names (customer_id, ticket_text) so the agent knows what to pass
Return concise, structured outputs the agent can act on
Add idempotency where possible — agents sometimes retry on failure

Instruction snippet for the agent:


When calling this workflow tool:
 
1. Confirm required inputs before calling.
2. Pass only the fields the workflow expects.
3. On failure, return the error reason and suggested next step.
4. On success, return the key output fields.

Next steps

Creating Workflows: Build from first principles
Running Workflows: Execute via UI, API and SDK
Environments: Promote safely to production

Built with ❤️ by Scout OS