Migrate from Bannerbear to Orshot

# Migrate this project from Bannerbear to Orshot

You are helping me move from Bannerbear (api.bannerbear.com) 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 Bannerbear touchpoint in this project

Search for, and list with file paths:
- `api.bannerbear.com`, `sync.api.bannerbear.com`, `ondemand.bannerbear.com`
- the `bannerbear` npm/pip/gem package or SDK imports
- `BANNERBEAR` environment variables and API keys
- template UIDs (strings like `A89wavQyY4Bepx1ZjD`), V2 "modifications" arrays and V5 "objects" arrays
- webhook handlers that receive Bannerbear image events
- Signed URL / Simple URL builders (`/signedurl/`, `base64` modification encoding)
- n8n, Make or Zapier exports in the repo that contain Bannerbear nodes

## 2. Templates

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

Once imported, each Bannerbear layer name becomes an Orshot field name. V5 names carry over unchanged ("image-container" stays `image-container`); V3 labels become lowercase with underscores ("Hero Image" → `hero_image`). Ask me for the Orshot template IDs, or read the fields 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: Bannerbear template UID → Orshot templateId, and Bannerbear modification name → Orshot field key. Show it to me before editing code.

## 3. Rewrite the API calls

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

Bannerbear:
```http
POST https://api.bannerbear.com/v2/images
Authorization: Bearer BB_KEY
{ "template": "UID", "modifications": [ { "name": "title", "text": "Hello" }, { "name": "hero_image", "image_url": "https://…" } ], "webhook_url": "…" }
```

Orshot:
```http
POST https://api.orshot.com/v1/studio/render
Authorization: Bearer ORSHOT_KEY
{ "templateId": 12345, "modifications": { "title": "Hello", "hero_image": "https://…" }, "response": { "type": "url", "format": "png" } }
```

Rules:
- `modifications` is an object keyed by field name, not an array. Text and image URL values are plain strings.
- Style overrides use dot keys: `"title.fontSize": 48`, `"title.color": "#111"`. Docs: https://orshot.com/docs/dynamic-parameters
- Multi-page templates prefix the page: `"page2@title"`.
- `response.format`: png, jpg, webp, avif, pdf, mp4, webm, gif. `response.type`: url, base64, binary.
- Sync is the default: the response contains `data.content` (the file URL or data). Remove Bannerbear polling loops.
- If the code relies on webhooks, use async mode instead: add `"mode": "async"` inside `response`, plus top-level `webhook_url` and `metadata`. 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
- 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. Signed URLs and Simple URLs

Bannerbear Signed URLs (ondemand.bannerbear.com) become Orshot Dynamic URLs: https://orshot.com/docs/integrations/dynamic-urls
Shape: `https://api.orshot.com/v1/studio/dynamic-url/{name}.png?templateId=12345&title=Hello&sign=SIGNATURE`
- Only text fields can be set through the URL. Image swaps must go through the render API.
- The signature comes from the template's Quick Connect → Dynamic URL panel; ask me for it.
- Links already sent from ondemand.bannerbear.com keep working only while the Bannerbear account exists. Only update new sends.

## 5. Automations

- n8n: replace the Bannerbear 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 Bannerbear 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 Bannerbear 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 fields: 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 Bannerbear calls in place behind a flag until each Orshot render is compared with the Bannerbear output on real data.
- Render each mapped template once with test data and show me the URLs.
- Then remove the Bannerbear SDK, env vars and dead webhook handlers.

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