Use Flowboard for repeatable motion
Page-load entrances, simple hover states, click toggles, and basic scroll reveals are good candidates for native interactions.
GSAP to Webflow Interactions Converter
Flowboard can translate native-safe GSAP motion into Webflow ix3 interactions while preserving unsupported behavior as runtime fallback.
motion.js
gsap.timeline({ paused: true })
.to(".menu", { y: 0, opacity: 1 })
.from(".menu-link", { y: 16, stagger: 0.08 })
ScrollTrigger: { trigger: ".hero", start: "top 75%" }
GSAP page load (2 actions)
Elevate Your Design.
Animate Everything.
Scroll down to see ScrollTrigger in action. Smooth, performant, and completely customisable animations.
Scroll
0.00 / 0.60
GSAP bf4da4e5-da2d...
GSAP 96bd34c7...
What maps today
This page reflects the supported GSAP shapes already present in the Flowboard extension repo today, not a speculative roadmap.
Direct GSAP tweens
Simple `gsap.from(...)`, `to(...)`, `fromTo(...)`, and safe setup `gsap.set(...)` calls can map into native interaction steps.
Click and hover triggers
Straightforward click, mouseenter, mouseleave, and simple toggle handlers can become native Webflow triggers.
ScrollTrigger support
Basic selector-based `ScrollTrigger` configs with static triggers and safe options can map when behavior can be preserved.
Timeline chains
Simple `gsap.timeline(...)` chains and reversed toggle patterns are recognized when the control flow stays predictable.
SplitText payloads
Simple class-targeted `SplitText.create(...)` and `new SplitText(...)` calls can carry over into native interaction payloads.
Correct fallback
When unsupported behavior is required, Flowboard preserves the block as runtime GSAP instead of emitting a misleading partial native action.
Convert native-safe GSAP into Webflow interactions
1
Paste markup and GSAP
Bring HTML, CSS, and native-safe or fallback GSAP snippets into Flowboard while you work inside Webflow Designer.
2
Generate native interactions
Flowboard resolves static selectors and emits Webflow ix3 interactions for native-safe load, click, hover, and simple scroll motion.
3
Keep the edge cases visible
Unsupported selectors, plugins, callbacks, repeat/yoyo, and unsafe style behavior stay surfaced as warnings instead of becoming broken hidden output.
JavaScript fallbacks
What stays as JavaScript
The extension intentionally leaves unsupported GSAP behavior visible. That is safer than pretending every animation can be flattened into ix3.
If a GSAP block needs unsupported style, callback, repeat/yoyo, plugin, or dynamic selector behavior, Flowboard preserves that block as fallback instead of emitting a partial native action that changes what the animation does.
Unsupported or unsafe style props
`filter`, `clipPath`, unknown style props, and direct style-only `to(...)` tweens without a known start state fall back for correctness.
Advanced ScrollTrigger setups
`pin`, `snap`, lifecycle callbacks, custom scrollers, and more complex trigger behavior still sit outside current ix3 coverage.
Complex selectors and control flow
Sibling selectors, attribute selectors, pseudo elements, nested conditionals, and custom playback state are still too loose to map safely.
Broader runtime side effects
Class toggles, DOM mutations, and app-state logic mixed into handlers remain supplemental runtime behavior rather than native ix3.
When to use Flowboard instead of rebuilding interactions manually
Use Flowboard when the GSAP intent is clear enough to map, and use manual rebuilds when the animation depends on custom runtime behavior.
Keep rebuilds for custom systems
Advanced plugins, custom scrollers, callbacks, DOM mutation, and app state are usually better handled as intentional JavaScript.
Use warnings as a planning tool
Flowboard surfaces what mapped and what did not, so you can decide what to keep native and what to refine manually.
Use GSAP where it fits, keep Webflow editable where it matters
Pair this with Flowboard’s HTML to Webflow converter so structure, classes, and supported motion land in the same workflow.