Workflow builder or solution administrator
Start from a proven pattern without skipping review
Templates reduce blank-canvas work. They do not know your permissions, provider accounts, field meanings, approval policy, or failure owner. FlowOS therefore installs reusable patterns as inactive drafts.
Before you start
- Permission to view and install templates.
- The target connectors and business owner are known.
#Choose by business outcome
Prefer a template whose trigger and outcome match your process. For Northstar, a lead qualification or high-value lead approval recipe is closer than a generic webhook template. Read required connectors, fields, permissions, and readiness notes before installation.
#Adapt the installed draft
- Install into the intended workspace and folder.
- Rename it using business language.
- Map template fields to the capture form and lead record.
- Replace placeholder recipients and connector references.
- Review approval and failure routes.
- Run the same validation and test matrix as a hand-built workflow.
#Treat packs as coordinated starter data
An industry pack may install forms, pipeline terms, recipes, connector guidance, and workflow drafts together. Review every artifact and remove unused examples. Never assume that sample credentials, mappings, or provider claims are production-ready.
#Common mistakes
- Publishing immediately after installation.
- Keeping sample recipients or provider IDs.
- Installing several overlapping packs without ownership.
#Verify the result
- The selected pattern matches the business event.
- Mappings and recipients were replaced.
- Unused artifacts were removed.
- The installed draft passed ordinary workflow tests.