Install a template

1. Open the template, or a single component, and choose Install.
2. Choose the workspace. Next.
3. If the package contains SQL, choose the database connector. The label is Database connector. Next.
4. Read the review. It groups components into Workflows, Workflow nodes, Apps, Agents, SQL scripts, and JavaScript (manual).
5. For SQL, open each script. Run AI risk check when you want a written risk note. Tick I reviewed the SQL and want to run it.
6. Choose Install.

You should see a result list: a count installed, and manual or failed when those happened. Workflows arrive turned off. Apps arrive private. Open each one before you enable a trigger or publish an app.

The review says Already in workspace when an app, workflow, or agent with the same name is already there. Installing again creates another copy with that name. Continue when you want the copy. SQL and JavaScript are not part of this name check.

On the result step, Check with Chat opens Intelligence on this workspace with the install summary. Use it to see which apps, workflows, and agents landed, and which credentials you still need. The setup guide on the template page is the other place those steps are written.

• Install stays off while SQL is present and the checkbox is clear, or while no workspace is selected.
• The selected workspace has no SQL connector. Add a SQL connector in that workspace, or pick another workspace.
• AI features require API keys configured in workspace settings. The risk check needs that. You can still tick the SQL checkbox and install after you have read the script yourself.
• Component code is missing. or Component code is not valid JSON. The author saved an empty or broken component. Fork it only if you can repair the code.
• A SQL connector is required to run this snippet. Go back and pick the database connector.
• A row marked manual is JavaScript. Copy it from the component. A row marked failed shows the message on that row. The other components in the same install still complete.