Migrate from Templated to Orshot

# Migrate this project from Templated to Orshot

You are helping me move from Templated (api.templated.io) to Orshot (api.orshot.com). Orshot renders images, PDFs and videos from templates through an API, and has native n8n, Make, Zapier, Pipedream and Airtable apps plus an MCP server (https://mcp.orshot.com/mcp, setup at https://orshot.com/agents). If you can connect to that MCP server, do it first: it lets you list my Orshot templates, read their parameters and test renders directly. Read the docs linked below before changing anything, then do the work in the order given.

## 1. Find every Templated touchpoint in this project

Search for, and list with file paths:
- `api.templated.io`, `cdn.templated.media`, `templated-assets.s3.amazonaws.com`
- the `templated` npm/pip package or SDK imports
- `TEMPLATED` environment variables and API keys
- template IDs (UUIDs like `a55fc2e0-d651-4864-9308-a601307e62fb`) and `layers` objects keyed by layer name
- `GET /v1/render/{id}` polling loops and `webhook_url` handlers that receive render events
- Templated's embedded editor (`@templated.io/editor` or an iframe of app.templated.io)
- n8n, Make or Zapier exports in the repo that contain Templated nodes

## 2. Templates

Templates cannot be converted from code alone. I will import each Templated template into Orshot myself (New Template → Templated tab → upload the editor page saved as .mhtml). Guide: https://orshot.com/migrate/from-templated

Once imported, each Templated layer name is an Orshot parameter with the same name ("text-1" stays `text-1`, "image-2" stays `image-2`). Ask me for the Orshot template IDs, or read the parameters with:
- GET /v1/studio/templates/{id}: https://orshot.com/docs/api-reference/studio-template-get
- List templates: https://orshot.com/docs/api-reference/studio-templates-list

Build a mapping table: Templated template ID → Orshot templateId. Show it to me before editing code.

## 3. Rewrite the API calls

Reference: https://orshot.com/docs/api-reference/render-from-studio-template

Templated:
```http
POST https://api.templated.io/v1/render
Authorization: Bearer TEMPLATED_KEY
{ "template": "UUID", "layers": { "text-1": { "text": "Hello", "color": "#111" }, "image-1": { "image_url": "https://…" } }, "format": "png" }
```

Orshot:
```http
POST https://api.orshot.com/v1/studio/render
Authorization: Bearer ORSHOT_KEY
{ "templateId": 12345, "modifications": { "text-1": "Hello", "text-1.color": "#111", "image-1": "https://…" }, "response": { "type": "url", "format": "png" } }
```

Rules:
- `modifications` is a flat object keyed by parameter name. A text layer's `text` and an image layer's `image_url` become the value itself.
- Layer properties become dot keys: `color` → `"text-1.color"`, `background` → `"text-1.backgroundColor"`, `font_family` → `"text-1.fontFamily"`, `font_size` → `"text-1.fontSize"`, `hide: true` → `"text-1.opacity": 0`. Docs: https://orshot.com/docs/dynamic-parameters
- Templated `pages: [{ page, layers }]` becomes page-prefixed keys: `"page2@text-1"`. Keys without a prefix apply to every page.
- `response.format`: png, jpg, webp, avif, pdf, mp4, webm, gif. Templated defaults to jpg; Orshot defaults to png, so set it explicitly if the format matters. `response.type`: url, base64, binary. `response.scale` replaces Templated's `scale`.
- Both APIs are synchronous by default. The Orshot response carries `data.content` (the file URL or data) instead of Templated's `url`. Remove any `GET /v1/render/{id}` polling.
- If the code uses `async: true` or `webhook_url`, use Orshot's async mode instead: add `"mode": "async"` inside `response`, plus top-level `webhook_url` and `metadata` (Templated's `external_id`). You get `202 { id, status: "queued" }`; the webhook body is `{ event: "render_job.finished", job }`; or poll GET /v1/studio/render-jobs/{id}. Docs: https://orshot.com/docs/api-reference/async-render-start
- `width`/`height` overrides have no equivalent: Orshot renders at the template size (use `response.size` or `response.scale` instead). `cmyk: true` becomes `pdfOptions: { colorMode: "cmyk" }`. `transparent`, `flatten`, `merge`, `zip`, `templates[]` have no equivalent; flag them to me.
- Auth stays Bearer. Store the key as `ORSHOT_API_KEY`. Keys: https://orshot.com/docs/quick-start/get-api-key
- Official SDKs (Node, Python, Ruby, PHP) if you prefer them over fetch: https://orshot.com/docs/sdks
- Error codes: https://orshot.com/docs/error-reference

## 4. Embedded editor

Templated's embedded editor becomes Orshot Embed: https://orshot.com/docs/orshot-embed/introduction
Ask me before touching this; it needs an embed key from the Orshot dashboard and a plan that includes Embed.

## 5. Automations

- n8n: replace the Templated node with the Orshot node (community package `n8n-nodes-orshot`). Docs: https://orshot.com/docs/integrations/n8n. I can also paste a ready workflow from the template's Quick Connect → Copy as → n8n workflow.
- Make: replace the Templated module with the Orshot module, or import the blueprint from Quick Connect → Copy as → Make blueprint. Docs: https://orshot.com/docs/integrations/make
- Zapier: replace the Templated action with Orshot → "Generate Image from Studio Template". Docs: https://orshot.com/docs/integrations/zapier
- Pipedream: https://orshot.com/docs/integrations/pipedream
- Anything that only speaks HTTP: Orshot's inbound template webhook accepts any JSON and maps keys to parameters: https://orshot.com/docs/integrations/webhooks
- If I use AI agents: Orshot for agents (MCP, skills): https://orshot.com/agents
  - MCP server URL: https://mcp.orshot.com/mcp (Claude, ChatGPT, Cursor, Codex and any MCP client). Docs: https://orshot.com/docs/integrations/mcp-server

## 6. Verify, then switch

- Keep Templated calls in place behind a flag until each Orshot render is compared with the Templated output on real data.
- Render each mapped template once with test data and show me the URLs.
- Then remove the Templated SDK, env vars and dead webhook handlers.

Full API index for anything not covered: https://orshot.com/llms.txt