A project to help users start Jotform Workflows with ready-made use cases and integrations.
One general builder page for every task.
A landing page for each use case and integration. The user finds a ready-made automation, clicks the CTA and starts building.
Workflows had only one general builder page. A user who wanted to automate a task, for example “text me when a new email arrives”, landed there and saw a prompt field.
There were only a few example prompts, and they might not match what the user needed. So most users had to figure out the workflow alone, and automation looked hard.
There are hundreds of use case and integration pairs. A page for each one can't be designed by hand.
n8n: long and technical. It doesn't show the workflow working.
Make: clean but static. Two app icons, no steps in between.
What I took from this: show the workflow working, for the user's own task.
No competitor had a one-to-one match for what we built: an animated, use-case-specific hero for each integration.
…they will understand faster what it does, and they will start building.
And if AI can make these visuals (hero animations, thumbnails and other page visuals) for each use case, I can cover hundreds of pages without designing each one by hand.
Each one shows a workflow in a different way and can fit any use case. I tested them with 7 participants in a think-aloud test.
participants · think-aloud test
2 use AI tools often · 3 a few times · 2 never
picked Variation 1 as the clearest
found Variation 1 the most AI-powered
think the product can handle many automations
feel they could build another workflow alone
“It shows exactly what is going to happen.”on Variation 1
“Variation three helps me understand there are many other things it can do.”on Variation 3
“Variation two is very simplistic.”on Variation 2
“I would like to see the connections between the apps.”on Variation 3
Variation 1 gave the clearest direction. The plan was to use one animation on all landings, so the trigger and action got general names.
Then I saw that AI could turn the trigger and action parts into a skill. So I shaped them for each use case, and a Codex skill now creates a Lottie hero for any use case.
skill: use-case-hero-animation built with: Codex input: use case (apps + event + details) rules: workflow node · glow #8A38F5 → #0075E3 use-case details on nodes · verb from action output: hero-animation.lottie.json
When the prompt field was removed, the integration hero needed a new design. My solution was a simple 2‑step workflow. Small animations show each step clearly.
A badge appears
The line glows
It shows what it does
Then it starts again
for his help with the small animations.
Every use case needs a thumbnail in the directory where it is listed. Making each one by hand would take too much time. So I set the visual style first. Then Codex creates a thumbnail for each use case. For the Podo images, I connected the Magnific MCP to Codex. I can reuse this skill later on features pages.
skill: use-case-thumbnail built with: Codex + Magnific MCP input: use case (trigger app → action app) rules: Jotform visual style · app icons · brand colors one clear trigger → action story output: thumbnail.png
Skill output: a thumbnail
In the directory: jotform.com/ai/workflows/tools
Each landing has four Benefits cards, and each card has its own animation for that use case. Example: Gmail to SMS. Hover a card to play it.
New email alerts
Sender-based routing
Message details
Follow-up tracking
Burak created these animations with Claude and turned them into a skill. The skill made the Benefits visuals for all landings.
The steps and the layout stay the same. Only the app icons and names change for each use case.
This section lets users discover other integrations for the same apps. If they find one they want, Use Automation takes them straight to the builder, without opening its page.
In the reviewed sessions, some users found other automations this way.
Before, the CTA opened the Workflow Builder. It is powerful, but there are many choices on the first visit.
With the wizard, the user connects both accounts and sets up the trigger and action on the same page.
We watched JotStory recordings of real users as a team. Design issues and what we could fix, we fixed. The rest went to the related teams.
Users saw the CTA but not the animation. They didn't understand what the page offered, so they didn't click.
Mobile hero redesigned: the animation and the CTA are both visible above the fold.
On desktop and mobile, many users clicked the workflow nodes again and again before they found the CTA.
The animated hero stays, as requested. This issue is still open.
Some users moved to other landings through the breadcrumb and Discover other automations, or watched the how-to video.
The page structure supports discovery. It stays the same on all landings.
The prompt modal made users leave. Sign-up modals repeated, Excel and Sheets sign-in failed, SMS codes didn't arrive.
Prompt removed from the builder. The rest shared with the related teams.
Benefits not loading, a JS conflict, a missing template, a slow builder (25–40 s), a stuck button in the wizard.
Benefits, JS conflict and missing template fixed. The rest shared with the teams.
Which one gets more workflows? A: integration landing · B: wizard · C: template page. Running on Microsoft Excel to Google Sheets, the page with the most traffic.
170 of 2,666 users created a workflow
135 of 2,665 users created a workflow
146 of 2,666 users created a workflow
7,997 users so far · Early data, the gaps are not final.
Across all landings: 5 integration landings run this A/B/C test. The other 90 run an A/B test: landing vs. template.
CTA click rate · workflows created · workflows turned on
How far they scroll · clicks to other use case pages
Time per landing · pages per month
Time to make the visuals for one landing: by hand vs. with the skills
integration landings
made with the skills
use case landings
made with the skills
Users who created a workflow
No clear winner yetThe test is still running.
A/B/C numbers: 7,997 users so far on the Microsoft Excel to Google Sheets page.
How users moved through the landings from Aug 22 to Nov 10, 2026.
of sessions led to a workflow clone
of sessions led to a sign-up
average session duration
GA4, unsampled, 81 days. Steps are event and session counts, so the rates between steps are approximate.
The clear trigger → action hierarchy won the user test. 5 of 7 participants picked it as the clearest.
All 120 live landings were built with the skills. Each section follows its own rules, from hero motion to use-case-specific Benefits interfaces.
Hero and How it works share one structure across landings. Only icons and content change, so users see a familiar pattern on every page.
In 6 months, one landing grew into four entry points. The system was flexible enough to support prompt, integration, template and wizard.
Seven think-aloud sessions were enough to choose a direction for the hero.
Session reviews showed where users got stuck, so the team could find the issues and fix them.
Users clicked the workflow nodes again and again. The hero reads as UI, not as a demo. This is still open.
The animation was below the fold, so users saw the CTA without understanding the page. I redesigned it.
A few example prompts did not match what users needed. On integration landings, a clear 2-step workflow worked better.
After the CTA, many users met modals and sign-in steps in the builder. This part was outside the landing, but it affected the results.
Not one after the other, so the whole design works on both.
What the animation explains, where it points and what is clickable.
Agree on the rules before generating many pages.
Stay in closer contact with the product teams, so the landing and the builder steps work as one journey.
Check the iterated hero with users before using it on every page.
When a visual repeats on many pages, write it once as a skill: style rules, good examples and a clear input. Anyone can then generate visuals that follow the design language. The heroes, thumbnails, Benefits and How it works visuals were made this way.
A skill one designer builds can serve the whole team. The Thumbnail skill made the visuals for all landings in this project, and it can be adapted for features pages next. When the output is off, fix the rule, not each file.
Check animations and visuals on desktop, tablet and mobile before going live. What works on one screen can hide the message on another.
Session recordings let us check our design assumptions with real users. They can reveal paths we didn't expect, and some of them may turn into the next design improvements.