What a template contains

A template is the components you put in it, plus the page that explains them.

Read a template before you install

  1. Open the template from Templates, Categories, or Explore.
  2. Read the description and the setup guide on the page.
  3. Look at the components listed on the page. Each one is one installable piece.
  4. Open a component when you need to see its code before you install the package.

You should see Install. The setup guide is the author's steps for wiring the result in a workspace. Follow it after install. Credentials, connectors, and API keys are not copied from the author's workspace. You connect those in yours.

The same component in more than one template

A component can sit in more than one of your templates. Adding it to a second template does not copy it. A later edit of that component is the component both templates install.

Fork template asks to create a private copy of the template and its components. You then edit the copy under My Templates. Duplicate is the same action when you already own the template.

If this fails: you cannot tell what will be created

Open each component and read its kind: app, workflow, agent, SQL, or code. The install review lists the same groups: Workflows, Workflow nodes, Apps, Agents, SQL scripts, and JavaScript (manual). If a component says Unsupported, install of that piece fails and the others still run.