/interactions

name: webflow-mcp:interactions
version: 2026.09.21
description: Create, update, list, and delete Webflow IX3 interactions (GSAP animations) through Webflow MCP. Use when the user wants click/hover/load/scroll/mouse-move animations, interaction timelines, or data_interactions_tool / create_interaction payloads.

<!-- CHANGELOG 2026.09.21 — Stable GA follow-up. `webflow_guide_tool` includes a short Interactions section; payload shapes still come from action `guide`. Dropped the monorepo PR citation for WFS. `wf:variable`, `wf:rive`, and `wf:animate-rive` are default-on; call `guide` for their shapes. 2026.09.20 — IX3 interaction APIs are GA. Removed the beta endpoint, the `ff-ix3-interaction-apis` flag, and the gate-check step. `data_interactions_tool` is on the stable MCP server for every caller now.

• An empty `list_interactions` result is not proof a site has no interactions: the tool

reads IX3 only, so an IX2 site reads as empty. Added as Phase 1 step 5 and to the rejects index. 2026.09.16 — Session 2 re-read against the live host.

• The `guide` action and `webflow://guides/interactions` are live (CF #461).

The "not live / in review as #399" sentence was false. Prefer `data_interactions_tool` → `guide` for payload shapes; this skill is the workflow around them. `references/` stay for set-pieces the guide does not carry. 2026.08.30 — Three corrections found by re-reading our own claims against merged PRs.

• The role-form hover remove-button warning was true when written and was fixed by

webflow#117817 on 2026-08-19. Reattributed to that PR rather than called false.

• `playInReverse` is not an authorable replacement for `autoReverse`. webflow#118489

rejects it; there is no API-side replacement. The earlier entry below is wrong.

• Advanced eases are simply authorable. No write-boundary guard exists and the gate

is 100% public and stale, so the `[FLAG]` framing promised a refusal that cannot happen. 2026.08.26 — Corrections from a 135-interaction stress run (197 write attempts, 31 browser assertions). The gaps were almost all in the positive direction — not "which payloads are refused", which measured 46/48 accurate, but "what shape does this accepted field take".

• `wf:any-element` value is `'*'`, not `''`. It does not share a value with the

other two action-only keys. Highest-cost error in the run: eight relationship rows sent as a batch on the documented value, all refused.

• `wf:attribute` also takes a full selector. A bare name matches every element

carrying the attribute, which is ambiguous when several do.

• The hover recommendation is now one weak preference (prefer the split because

the panel writes it) instead of opposite defaults here and in the pack. A Designer check then disproved the remove-button penalty the role form was said to carry: both forms show a delete control on both action groups, so there is no editability tradeoff to trade against.

• References re-published from the corrected pack, which also adds the

`wf:lottie` / `wf:spline` value shapes, the `ix3-*` wrapper shapes, the `{from,to}` exception for plugin namespaces, `playInReverse`'s location, a `[FLAG]` tag distinct from `[GATED]`, and the MCP-vs-host ordering on the conditions guard. 2026.08.25 — Dogfood corrections against Webflow MCP 2.0.1.

• Added the silent-strip rule for unknown `config` keys (the single most

expensive trap on this surface — it cost a dogfood run three misfiled bugs).

• Documented `timing.ease` / `timing.stagger.ease` as an integer index into

EASING_NAMES, with the full 0–30 table, plus the advanced-ease object union. Previously undocumented in every file.

• Documented the `wf:class` `{operation, selectors}` shape.
• Documented the `stagger` object, the `filterContext.relationship` enum,

`wf:selector`, the `wf:inst` `[componentId, elementId]` shape, `wf:attribute`, and the per-interaction caps.

• Added `"tt": 2` to Examples 1–3. As written they paired a [from,to] array with

an omitted tween type, which is a measured no-op on a default element. Example 1 also gained the rest-state note: a FromTo holds its from-state, so the click example renders at `opacity: 0` until clicked, which reads as a failed write unless the agent says so.

• Corrected the hover-split section: `eventMode` is `pluginConfig.eventMode`

with values 'enter'/'leave'.

• Added Example 6 (custom JS event) including the Webflow.require('ix3').emit()

firing call, which appears nowhere else in the pack.

• Noted the tool-schema errata for conditionalPlayback and the siteId/site_id

placement split across the tool family. -->

Interactions

Create and edit IX3 interactions (GSAP animations) through Webflow MCP.

Important Note

**ALWAYS use Webflow MCP tools for all operations:**

• Use Webflow MCP's `webflow_guide_tool` to get best practices **before any other tool call**. It includes a short Interactions section that names `data_interactions_tool` and tells you to call action `guide` before writing. Payload shapes come from that `guide` action, not from the short section.
• Use Webflow MCP's `data_sites_tool` with action `list_sites` to identify the target site
• Use Webflow MCP's `data_pages_tool` with action `list_pages` to find the target page by name or slug
• Use Webflow MCP's `data_interactions_tool` for guide / list / get / create / update / delete
• Use Webflow MCP's `data_style_tool` to resolve class **style-block ids** before targeting `wf:class`
• DO NOT use any other tools or methods for Webflow interaction CRUD
• All tool calls must include the required `context` parameter (15-25 words, third-person perspective)
• **No Designer or MCP Bridge required.** `data_interactions_tool` is headless, the same way `data_element_tool` is. Designer is only useful afterward, to inspect the Interactions panel or Preview. Do not ask the user to