> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sitecopilot.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# n8n Templates Library (Sitecopilot Standard)

This page lists the **standard n8n templates** provided for Sitecopilot. They are importable JSON workflows you can use as‑is or customize.

## Download

* From the repository: navigate to `_n8n/templates/` and download the `.json` files you need.
* Each file name reflects its purpose, e.g., `sitecopilot-bulk-create-pages.json`.

## Install

1. Open n8n → **Workflows** → **Import from File**.
2. Select the downloaded JSON file.
3. After import, open the workflow → set required **Credentials** or **Environment variables** (see below).

## Required credentials / env

Most templates expect these variables:

* `SITECOPILOT_TENANT_BASE_URL`, `SITECOPILOT_TENANT_TOKEN` (tenant operations)
* `SITECOPILOT_ADMIN_BASE_URL`, `SITECOPILOT_ADMIN_TOKEN` (central operations; only for templates that manage tenants)

Define them as **Credentials** or **Environment variables** and reference via expressions (`{{$env.VAR}}`) where indicated in node params.

## Templates included

* **Bulk Create Pages** — CSV → `POST /api/page` per row with validation and summary.
* **Content Update Pipeline** — input JSON → `PUT /api/content` and notify editor.
* **Asset Uploader** — folder or S3 → `POST /api/asset` → attach URLs via `PUT /api/content`.
* **Nightly Sitemap Snapshot** — cron → `POST /api/sitemap` → persist JSON.
* **Contact Form Intake** — n8n webhook endpoint receives form JSON → branch to Slack/Email/CRM.
* **Tenant Bootstrap (Central)** — create tenant, issue token, seed starter content.

> You can combine templates or use them as sub‑workflows.

## Customization guidelines

* Keep HTTP nodes generic; pass base URLs and tokens via env/credentials.
* Add **error branches** and **retry** for transient failures.
* Log important IDs (page url, tenant id) at each step for traceability.

## Maintenance & versions

* Check the repo for updates to templates; version tags indicate changes.
* When upgrading, import new JSON side‑by‑side, diff node params, and migrate credentials.