The second time you build a lead-intake workflow, you shouldn't be rebuilding it — you should be copying the one that already works. FluidGrids treats every proven workflow as a potential template.
The templates gallery shows two sources side by side. Workspace templates are your own active workflows, categorized automatically — Data Processing, Integration, Automation, AI/ML, Communication — so the team's best work is browsable, not buried in a list. Store templates come from the platform store, packaged for reuse across workspaces.
Duplicating a workspace workflow creates a fully independent copy under a new workflow key: same graph, same configuration, fresh version history. Edit the copy as much as you like — the source is never mutated. It's the safe way to fork a production automation for a new variant.
Importing from the store goes further: the new workflow records exactly which template it came from, with the source template's id stamped into the copy. That lineage means you can always answer "which of our workflows came from the v2 onboarding template?" — essential when a template improves and you need to know who's running the old shape.
Crucially, credentials never travel with a template. An imported workflow arrives with its connection slots unset, and the builder's required-field validation flags every unbound credential adapter before activation. You rebind the new workspace's own connections — secrets stay where they belong, and the template stays portable.
Do it yourself
Skip the blank canvas by duplicating a proven workspace workflow or importing a packaged store template — with source lineage recorded and credentials left for you to rebind.
Open the Templates page to browse workspace templates and store templates side by side.
You should see: A gallery of reusable workflows loads with category filters and search.
Ready to make this your story?
