Templates

A template is a prebuilt project or rule set you can import as a ready-made starting point, so you begin from working logic instead of a blank canvas.

What a template is

Where an extension adds one callable capability, a template captures a whole arrangement of authoring artifacts — rule sets, rules, conditions, and actions — that solve a common scenario. Importing a template copies that arrangement into your own project, where you are free to edit it. Like extensions, templates have a stable identity, published versions, and engagement signals (views, likes, favorites) that surface the most useful ones.

Importing a template

Browse the catalog, open a template to review its description and version history, then import it. Importing performs a remix: the engine clones the template's published content into a new project (or into an existing project) that belongs to your organization. The copy is independent of the original, so later changes to the source template never alter what you imported, and your edits never affect the template.

Saving your own rule set as a template

Any project you own can become a template. The save-as-template flow snapshots the current project and publishes it as a reusable template under your organization. You give it a name, description, and category, and choose whether it is public (eligible for the marketplace and the public site) or private (visible only within your organization).

1. Open the project whose logic you want to share.
2. Choose to save it as a template and fill in the marketplace details.
3. Publish a version so other users — or just your own future projects — can import it.

Versions

Templates are versioned the same way extensions are. Publishing a new version leaves prior versions in place, and consumers import a specific published version. This lets you evolve a template over time without disrupting anyone who already imported an earlier one.