Template Library Overview
We come with 219 workflow templates, organized by 10 industry categories, covering various scenarios from app operations to finance, medical care, and education.
Braidrun ships with 240+ workflow templates. This page first explains what the template library actually is, then shows you the full picture.
Designing a production-level AI workflow from scratch is a tiring task: you have to think clearly about step splitting, Agent role division, variable transfer, approval nodes, exception handling, cost control... These are all experiences that can only be summed up after going through pitfalls.
Every entry in the template library has already worked through the questions above and run in real business scenarios. Cloning one and tweaking the parameters is much faster than starting from a blank YAML.
240+ Templates, Organized Into 10 Industry Categories
List Of Industry Categories
Below are the ten main industry categories. Each has templates at varying complexity, from quick validation to end-to-end production:
| Industry Categories | Common Scenarios | Give Some Representative Templates |
|---|---|---|
| Application/App Operation | App package, certificate monitoring, ASA optimization, ASO, subscription renewal tracking | apple-search-ads-campaign · aso-optimization-workflow · dingyue-certificate-expiry-monitor |
| Advertising/Marketing | Google Ads / Facebook Ads, content marketing, SEO, brand crisis PR | google-ads-campaign · content-marketing-seo · brand-crisis-pr |
| software engineering | Code review, CI/CD, PRD review, technical solution design | code-review · ci-cd-pipeline · service-architecture-design |
| Content Creation | Short video scripts, podcasts, e-books, email newsletters, course design | content-creator-short-video · content-creator-podcast · content-creator-newsletter |
| Data Analysis | A/B testing analysis, competitive product intelligence, weekly report generation, KPI attribution | ab-test-design-analyzer · competitive-intelligence-report · dingyue-weekly-business-review |
| Compliance/Approvals | Contract review, compliance policy gap analysis, approval life cycle management | business-contract-review · compliance-policy-reviewer · approval-lifecycle-state-machine |
| Finance / Banking | Loan approval, risk control, investment advice, insurance underwriting | banking-loan-application-processor · insurance-underwriting · fintech-* |
| Medical / Health | Medical record analysis, drug interaction examination, clinical decision aid | healthcare-* |
| Education/Training | Course outline, study plan, exam questions, Q&A assistant | education-* |
| Vertical industries | Agriculture, automobiles, aviation, hotels, energy, logistics… | agriculture-* · automotive-* · aviation-* · hotel-* · energy-* |
For a complete list and selection suggestions for each category, see Category Details and Representative Templates.
What exactly is in the template?
Each template is a complete workflow YAML containing:
- Description and tags — A sentence or two describing what it does, who it is suitable for, and what the prerequisites are.
- Complete DAG structure — All steps from input to output, dependencies and branches have been arranged according to "practical experience".
- Agent preset and model selection — Each LLM step is specified with an appropriate preset (e.g. reviewer / writer / coder) and temperature.
- Variable declaration and default value — All "business adjustable parameters" are distilled into variables sections, and you can see at a glance where to change them according to your situation.
- Credential Reference — By naming the reference, the key is not hard-coded. You only need to add a credential with the same name in the credential center to get it running.
- Example input and expected output — Supporting test data and a preview of "probably what can be run".
- Reasonable approval and exception handling — Manual_approval is preset before high-risk steps (outbound messages, deductions, and going online).
After cloning, the template becomes "your workflow". You can change every field, delete every step, and add your own credential references - the platform won't lock it away. Reading YAML is like reading a commented Python script.
Templates Vs Modules
Many people use these two words easily for the first time:
- Templates(Template)—a starting YAML document that evolves independently once cloned. A new template version won't automatically alter your copy; when you want to follow it, you can preview the diff and upgrade with one click. SeeInstantiate from Templatethe "Template upgrade" section.
- Module(Module) - a "sub-process that can be referenced by other workflows". After the referenced party is upgraded, the caller automatically uses the new version. Suitable as a "reusable black box".
An analogy: templates are like "npm init scaffolding" and modules are like "npm install dependencies". See details Modularization and Reuse.
How to Choose the Right Template
- First filter by industry category – confirm the field you want.
- Look at the "prerequisites" in the description - which credentials are required and which systems are accessed. Leave the missing parts in the next step and make up for them later.
- Look at the estimated time and cost - it will take about a few minutes to run down at a time, and it will cost a few cents/a few dollars/tens of dollars.
- Choose one with similar complexity - prefer to start with a simple version and then use the AI assistant to expand it as needed; don't choose a complex template and then delete it.
- Dry-run first - after cloning, no matter whether you change it or not, run it first to see the DAG structure and variable flow.
Next
- Instantiate a Workflow from a Template — The most recommended user path, step by step
- Category Details and Representative Templates — 10 major categories, selected representative templates for each category
- Open the template library directly — Browse, filter, and search within products