webflow-data-handling
/webflow-data-handling
Design data minimization, retention, access, and deletion workflows for Webflow forms, ecommerce, CMS, logs, and webhooks. Use when personal data enters an integration or compliance evidence is needed. Trigger with "Webflow privacy", "Webflow data retention", or "delete Webflow user data".
- Author
- jeremylongshore ↗
- Repository
- tons-of-skills-marketplace ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Design data minimization, retention, access, and deletion workflows for Webflow forms, ecommerce, CMS, logs, and webhooks. Use when personal data enters an integration or compliance evidence is needed. Trigger with "Webflow privacy", "Webflow data retention", or "delete Webflow user data".
Triggers from the description
Arguments
/webflow-data-handling [project-path] [data-flow]
Original author description
Design data minimization, retention, access, and deletion workflows for Webflow forms, ecommerce, CMS, logs, and webhooks. Use when personal data enters an integration or compliance evidence is needed. Trigger with "Webflow privacy", "Webflow data retention", or "delete Webflow user data".
How it works
- Overview
- Prerequisites
- Tool Discipline
- Current Contract
- Authentication
- Workflow
- Approval Boundaries
- Output
- Error Handling
- Examples
SKILL.md preview
--- name: webflow-data-handling description: >- Design data minimization, retention, access, and deletion workflows for Webflow forms, ecommerce, CMS, logs, and webhooks. Use when personal data enters an integration or compliance evidence is needed. Trigger with "Webflow privacy", "Webflow data retention", or "delete Webflow user data". argument-hint: "[project-path] [data-flow]" allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit version: 1.6.0 author: Jeremy Longshore <jeremy@intentsolutions.io> license: MIT tags: - saas - webflow - privacy - data-governance model: inherit effort: medium compatibility: Designed for Claude Code --- # Webflow Data Governance ## Overview This skill produces a repo-grounded Webflow plan or implementation. It treats current official documentation and the target project's installed versions as authority, keeps discovery read-only, and separates preparation from live mutation. ## Prerequisites - A named target repository or project path and permission to inspect it - The intended Webflow environment and non-secret resource identities, or a plan to discover them read-only - Access to current official Webflow documentation; credentials stay in the user's existing secret store ## Tool Discipline Use `Read` for repository instructions and relevant files, `Glob` to inventory manifests and Webflow integration paths, and `Grep` to locate API hosts, IDs, scopes, and credential names. Use `WebFetch` only for current official Webflow documentation. Use `Write` for a new user-requested artifact and `Edit` for minimal changes to existing files after the evidence pass. ## Current Contract - Form submissions and ecommerce payloads can contain direct identifiers, free text, addresses, and order data; treat schemas as sensitive until classified. - Webflow scopes control API access but do not define your legal basis, retention period, or downstream processor obligations. - Deletion, unpublishing, and archiving have different effects. A compliance workflow must target the correct resource and verify downstream copies. - Generated examples are operational guidance, not legal advice; policy decisions require the organization's approved legal and security owners. ## Authentication Authenticate Data API calls with a bearer token selected for the integration: a site token for controlled single-site work, a workspace token only for its supported workspace/read use cases, or OAuth for user-authorized applications. Derive scopes from the exact endpoints. Never read, echo, persist, or place token values in commands, patches, examples, logs, or reports. ## Workflow 1. Inventory fields, event payloads, storage, logs, caches, exports, subprocessors, retention, and access roles for each data flow. 2. Classify required versus optional data and remove collection or persistence that the stated purpose does not need. 3. Redact sensitive fields before logs, traces, debug bundles, fixtures, and dead-letter queues. 4. Define access/export/delete requests as authenticated workflows with resource IDs, approvals, downstream propagation, and receipts. 5. Implement retention in each storage layer and test expiration plus legal-hold exceptions defined by policy. 6. Verify with synthetic data and report uncovered systems or unresolved policy choices to the accountable owner. ## Approval Boundaries Default to read-only inspection. Before any create, update, delete, publish, unpublish, archive, deploy, token revoke, or webhook registration, show the exact environment and resource IDs, the proposed change, validation method, and rollback or compensating action. Proceed only when the user's request clearly authorizes that mutation; require a fresh explicit approval for production publication or destructive work. ## Output Return the inspected project and versions, verified Webflow identities, relevant endpoint and scope contract, changes proposed or made, validation evidence, live-mutation status, rollback readiness, and remaining risks. Distinguish documented fact, repository evidence, and inference. ## Error Handling | Condition | Response | |---|---| | Subject identity uncertain | Do not export or delete; escalate to the approved identity-verification process. | | Deletion partially fails | Preserve per-system receipts and retry only after reconciling current state. | | Policy undefined | Stop at inventory and options; do not invent a legal retention period. | ## Examples For form submissions, retain only fields required for follow-up, redact payloads from logs, map downstream CRM copies, and make deletion an authenticated, approved, receipt-producing workflow. ## Resources - [Official Webflow references](references/official-docs.md) - [Webflow developer documentation](https://developers.webflow.com/) - [Data API v2 index](https://developers.webflow.com/data/v2.0.0/llms.txt)
Files in this package (2)
- SKILL.md 5 KB
- references/official-docs.md 1 KB
Versions
The database has no other skills named webflow-data-handling.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version d59c1c60be18 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100webflow-core-workflow-b
Plan Webflow Data API operations outside the core CMS item loop, including pages, components, forms, ecommerce, assets, and custom code. Use when a request spans site resources or needs endpoint-specific scope review. Trigger with "Webflow site API", "Webflow forms", or "Webflow ecommerce". - 100webflow-webhooks-events
Register and operate Webflow webhooks with current event names, signature verification, replay defense, and idempotency. Use when receiving site, CMS, form, ecommerce, page, or comment events. Trigger with "Webflow webhook", "verify Webflow signature", or "Webflow events". - 100webflow
Webflow is a visual website builder with a built-in CMS and hosting, plus a Data API v2 for managing content from code. Use when someone asks to "update Webflow CMS from a script", "sync content to Webflow", "publish a Webflow item", "Webflow webhook", "Webflow API", "connect… - 90privacy-retention-and-right-to-delete
Guides agents through privacy, retention, and deletion workflows in data systems. Use when handling personal data, retention limits, deletion requests, legal holds, or data minimization requirements across pipelines and published datasets. - 100webflow-webhooks
Receive and verify Webflow webhooks. Use when setting up Webflow webhook handlers, debugging signature verification, or handling Webflow events like form_submission, site_publish, ecomm_new_order, or collection item changes. - 100webflow-webhooks
Receive and verify Webflow webhooks. Use when setting up Webflow webhook handlers, debugging signature verification, or handling Webflow events like form_submission, site_publish, ecomm_new_order, or collection item changes.