Reuse templates and import workflows

Templates and exports help you start from an existing design. Review their resource references and behavior before running them in a different workspace or environment.

Choose a starting point#

Use Home → Pre-Built Workflows for workflow templates and App Store / App Templates for applications. Workflows → Import API supports the available API import flows.

Inspect what the template creates: controllers, actions, nodes, selectors, databases, schedules, and app dependencies. A template's name is not a guarantee that every destination resource is configured.

Import into a controlled scope#

1. Review the source and intended destination controller.
2. Preserve any existing workflow you intend to replace.
3. Import into a draft or isolated learning area where possible.
4. Check route/method collisions and entry/branch connections.
5. Rebind databases, WebSockets, and other resource IDs.
6. Configure sandbox and production selector values.

Secret values are omitted from template exports. Set them through the destination workspace's protected selector controls rather than expecting an import to recreate them.

Test before release#

Run representative sandbox requests and inspect actual upstream hosts and selected databases. Confirm external writes, messages, or schedules will target fixtures before executing them.

If using an import agent, inspect the resulting graph and configuration just as you would a manual import. A successful import means the artifact was accepted, not that every business path has been verified.

Export for reuse or recovery#

Use the supported controller/action export controls. Keep a complete export when preserving scripts, SQL, request bodies, and connections for recovery; a summary or slim tool response may omit essential fields.

Document the template's prerequisites, input/output contract, required selectors, and expected resource bindings. Store recovery artifacts where your team can find them without publishing private values.

See Postman for client collections and releases for version recovery.