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".
What this skill does
# 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 [email protected] --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
## Next Steps
For CI integration during upgrades, see `webflow-ci-integration`.
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.