webflow-upgrade-migration
Analyze, plan, and execute Webflow SDK upgrades (webflow-api v1 to v3) with breaking change detection, API v1-to-v2 migration, and deprecation handling. Trigger with phrases like "upgrade webflow", "webflow migration", "webflow breaking changes", "update webflow SDK", "webflow v1 to v2".
Best use case
webflow-upgrade-migration is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Analyze, plan, and execute Webflow SDK upgrades (webflow-api v1 to v3) with breaking change detection, API v1-to-v2 migration, and deprecation handling. Trigger with phrases like "upgrade webflow", "webflow migration", "webflow breaking changes", "update webflow SDK", "webflow v1 to v2".
Teams using webflow-upgrade-migration should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/webflow-upgrade-migration/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How webflow-upgrade-migration Compares
| Feature / Agent | webflow-upgrade-migration | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Analyze, plan, and execute Webflow SDK upgrades (webflow-api v1 to v3) with breaking change detection, API v1-to-v2 migration, and deprecation handling. Trigger with phrases like "upgrade webflow", "webflow migration", "webflow breaking changes", "update webflow SDK", "webflow v1 to v2".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Webflow Upgrade & Migration
## Overview
Guide for upgrading the `webflow-api` SDK and migrating from Webflow Data API v1
to v2. Covers breaking changes, endpoint mapping, import updates, and rollback.
## Prerequisites
- Current `webflow-api` SDK installed
- Git for version control (create upgrade branch)
- Test suite available
- Staging environment for validation
## Instructions
### Step 1: Assess Current Version
```bash
# Check installed version
npm list webflow-api
# Check latest available
npm view webflow-api version
# View changelog
npm view webflow-api --json | jq '.versions[-5:]'
```
### Step 2: SDK Version History
| SDK Version | API Version | Node.js | Key Changes |
|-------------|-------------|---------|-------------|
| 3.x | Data API v2 | 18+ | Current. `WebflowClient`, auto-retry, bulk ops |
| 2.x | Data API v1/v2 | 16+ | Transitional. Mixed v1/v2 endpoints |
| 1.x | Data API v1 | 14+ | Legacy. `Webflow` class, no types |
**v1 endpoints deprecation: late 2026.** Migrate before then.
### Step 3: API v1 to v2 Migration Map
#### Base URL Change
```
v1: https://api.webflow.com
v2: https://api.webflow.com/v2
```
#### Authentication Change
```typescript
// v1 (old) — API key
import Webflow from "webflow-api";
const webflow = new Webflow({ token: "your-api-key" });
// v2 (current) — Access token
import { WebflowClient } from "webflow-api";
const webflow = new WebflowClient({ accessToken: "your-access-token" });
```
#### Endpoint Migration Map
| Operation | v1 Endpoint | v2 Endpoint |
|-----------|-------------|-------------|
| List sites | `GET /sites` | `GET /v2/sites` |
| Get site | `GET /sites/{site_id}` | `GET /v2/sites/{site_id}` |
| Publish site | `POST /sites/{site_id}/publish` | `POST /v2/sites/{site_id}/publish` |
| List collections | `GET /sites/{site_id}/collections` | `GET /v2/sites/{site_id}/collections` |
| List items | `GET /collections/{id}/items` | `GET /v2/collections/{id}/items` |
| Create item | `POST /collections/{id}/items` | `POST /v2/collections/{id}/items` |
| Update item | `PUT /collections/{id}/items/{item_id}` | `PATCH /v2/collections/{id}/items/{item_id}` |
| List products | `GET /sites/{site_id}/products` | `GET /v2/sites/{site_id}/products` |
| List orders | `GET /sites/{site_id}/orders` | `GET /v2/sites/{site_id}/orders` |
**Key v2 differences:**
- Update uses `PATCH` (not `PUT`) — partial updates only
- Items created as drafts by default (`isDraft: true`)
- Bulk endpoints added (create/update/delete up to 100 items)
- Live (published) items have separate endpoints (`/items/live`)
- Scopes required (e.g., `cms:read`, `cms:write`)
### Step 4: SDK Method Migration
```typescript
// ===== v1 SDK (old) =====
const webflow = new Webflow({ token: "xxx" });
// List sites
const sites = await webflow.sites();
// List collections
const collections = await webflow.collections({ siteId: "site-123" });
// Get items
const items = await webflow.items({ collectionId: "col-456" });
// Create item
const item = await webflow.createItem({
collectionId: "col-456",
fields: { name: "Test", slug: "test", _archived: false, _draft: false },
});
// Update item (full replace)
await webflow.updateItem({
collectionId: "col-456",
itemId: "item-789",
fields: { name: "Updated", slug: "test" },
});
```
```typescript
// ===== v2 SDK (current) =====
const webflow = new WebflowClient({ accessToken: "xxx" });
// List sites
const { sites } = await webflow.sites.list();
// List collections
const { collections } = await webflow.collections.list("site-123");
// Get items (staged)
const { items } = await webflow.collections.items.listItems("col-456");
// Get items (live/published)
const { items: live } = await webflow.collections.items.listItemsLive("col-456");
// Create item (draft by default)
const item = await webflow.collections.items.createItem("col-456", {
fieldData: { name: "Test", slug: "test" },
isDraft: false,
});
// Update item (partial update via PATCH)
await webflow.collections.items.updateItem("col-456", "item-789", {
fieldData: { name: "Updated" }, // Only changed fields
});
// NEW: Bulk create (up to 100)
await webflow.collections.items.createItemsBulk("col-456", {
items: [{ fieldData: { name: "Item 1", slug: "item-1" } }],
});
// NEW: Publish items
await webflow.collections.items.publishItem("col-456", {
itemIds: ["item-789"],
});
```
### Step 5: Execute Upgrade
```bash
# Create upgrade branch
git checkout -b upgrade/webflow-api-v3
# Install latest
npm install webflow-api@latest
# Run tests to find breaking changes
npm test 2>&1 | tee upgrade-test-results.txt
# Fix breaking changes (common patterns above)
# ...
# Verify in staging
npm run test:integration
# Commit and PR
git add -A
git commit -m "upgrade: webflow-api to v3 (Data API v2)"
```
### Step 6: Rollback if Needed
```bash
# Rollback to previous version
npm install webflow-api@2.x.x --save-exact
# Or revert the upgrade branch
git revert HEAD
```
## Breaking Change Checklist
- [ ] Import changed: `Webflow` class to `WebflowClient` named export
- [ ] Auth changed: `token` to `accessToken`
- [ ] Method calls changed: `webflow.sites()` to `webflow.sites.list()`
- [ ] Field data wrapped in `fieldData` object
- [ ] Update method changed from `PUT` to `PATCH` (partial)
- [ ] Item status: `_draft`/`_archived` to `isDraft`/`isArchived`
- [ ] Response shape: items now under `.items` property with `.pagination`
- [ ] Scopes required for all operations
## Output
- Updated SDK to latest version
- All v1 endpoints migrated to v2
- Breaking changes fixed
- Tests passing on staging
- Rollback procedure documented
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| `TypeError: Webflow is not a constructor` | Using v1 import with v3 SDK | Change to `import { WebflowClient }` |
| `400 Bad Request` on create | Fields not in `fieldData` wrapper | Wrap fields: `{ fieldData: { ... } }` |
| `405 Method Not Allowed` | Using `PUT` instead of `PATCH` | Update to `PATCH` for item updates |
| Missing items in response | Not checking `.items` property | Destructure: `const { items } = await ...` |
## Resources
- [Migration Guide](https://developers.webflow.com/data/docs/migrating-to-v2)
- [SDK Releases](https://github.com/webflow/js-webflow-api/releases)
- [v2 API Reference](https://developers.webflow.com/data/reference/rest-introduction)
- [v1 Deprecation Timeline](https://developers.webflow.com/data/changelog/webflow-api-changed-endpoints)
## Next Steps
For CI integration during upgrades, see `webflow-ci-integration`.Related Skills
workhuman-upgrade-migration
Workhuman upgrade migration for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman upgrade migration".
wispr-upgrade-migration
Wispr Flow upgrade migration for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr upgrade migration".
windsurf-upgrade-migration
Upgrade Windsurf IDE, migrate settings from VS Code or Cursor, and handle breaking changes. Use when upgrading Windsurf versions, migrating from another editor, or handling configuration changes after updates. Trigger with phrases like "upgrade windsurf", "windsurf update", "migrate to windsurf", "windsurf from cursor", "windsurf from vscode".
windsurf-migration-deep-dive
Migrate to Windsurf from VS Code, Cursor, or other AI IDEs with full configuration transfer. Use when migrating a team to Windsurf, transferring Cursor rules, or evaluating Windsurf against other AI editors. Trigger with phrases like "migrate to windsurf", "switch to windsurf", "windsurf from cursor", "windsurf from copilot", "windsurf evaluation".
webflow-webhooks-events
Implement Webflow webhook registration, signature verification, and event handling for form_submission, site_publish, ecomm_new_order, page_created, and more. Use when setting up webhook endpoints, implementing event-driven workflows, or handling Webflow notifications. Trigger with phrases like "webflow webhook", "webflow events", "webflow webhook signature", "handle webflow events", "webflow notifications".
webflow-security-basics
Apply Webflow API security best practices — token management, scope least privilege, OAuth 2.0 secret rotation, webhook signature verification, and audit logging. Use when securing API tokens, implementing least privilege access, or auditing Webflow security configuration. Trigger with phrases like "webflow security", "webflow secrets", "secure webflow", "webflow API key security", "webflow token rotation".
webflow-sdk-patterns
Apply production-ready Webflow SDK patterns — singleton client, typed error handling, pagination helpers, and raw response access for the webflow-api package. Use when implementing Webflow integrations, refactoring SDK usage, or establishing team coding standards. Trigger with phrases like "webflow SDK patterns", "webflow best practices", "webflow code patterns", "idiomatic webflow", "webflow typescript".
webflow-reference-architecture
Implement Webflow reference architecture — layered project structure, client wrapper, CMS sync service, webhook handlers, and caching layer for production integrations. Trigger with phrases like "webflow architecture", "webflow project structure", "how to organize webflow", "webflow integration design", "webflow best practices".
webflow-rate-limits
Handle Webflow Data API v2 rate limits — per-key limits, Retry-After headers, exponential backoff, request queuing, and bulk endpoint optimization. Use when hitting 429 errors, implementing retry logic, or optimizing API request throughput. Trigger with phrases like "webflow rate limit", "webflow throttling", "webflow 429", "webflow retry", "webflow backoff", "webflow too many requests".
webflow-prod-checklist
Execute Webflow production deployment checklist — token security, rate limit hardening, health checks, circuit breakers, gradual rollout, and rollback procedures. Use when deploying Webflow integrations to production or preparing for launch. Trigger with phrases like "webflow production", "deploy webflow", "webflow go-live", "webflow launch checklist", "webflow production ready".
webflow-performance-tuning
Optimize Webflow API performance with response caching, bulk endpoint batching, CDN-cached live item reads, pagination optimization, and connection pooling. Use when experiencing slow API responses or optimizing request throughput. Trigger with phrases like "webflow performance", "optimize webflow", "webflow latency", "webflow caching", "webflow slow", "webflow batch".
webflow-observability
Set up observability for Webflow integrations — Prometheus metrics for API calls, OpenTelemetry tracing, structured logging with pino, Grafana dashboards, and alerting for rate limits, errors, and latency. Trigger with phrases like "webflow monitoring", "webflow metrics", "webflow observability", "monitor webflow", "webflow alerts", "webflow tracing".