Elementor gives creators an incredible visual workflow for building websites. Over the years, more users have been asking for deeper interaction possibilities—small dynamic behaviors, micro-interactions, and smarter connections between elements on the page.
We heard the requests.
We saw the patterns.
And we realized there was an opportunity to add something completely new on top of the existing ecosystem.
That’s how the Conditions Widget was created.
The goal was simple: Give users a way to define when something should happen, and what should happen, using a clean visual interface.
And the result became one of the most flexible interaction tools we’ve ever built.
Why We Decided to Create the Conditions Widget
For a long time, creators using Unlimited Elements asked us questions like:
“Can I trigger a class on click?”
“Can I hide or show something when another element is interacted with?”
“Can I make my own navigation buttons for sliders?”
“Can I control one widget from another?”
“Can I activate things based on time or date?”
These requests all pointed to the same idea: A need for simple, visual, logic-based interactions that go beyond styling.
Something lightweight.
Something flexible.
Something easy to understand.
So instead of adding small features here and there, we built a full interaction system that works inside Elementor’s editor, using a clear approach:
Trigger → Action → Target
Define the moment.
Define the reaction.
Define the element.
This gives creators the ability to build micro-interactions anywhere on the page, using the tools they already understand.
How the Conditions Widget Works
Inside the widget, you stack “Conditions,” which are basically small rules:
Trigger Type
What starts the interaction.Trigger Selector
Which element fires the trigger.Target Selector
Which element should respond.Action Type
What the target should do.
It’s a universal logic system that lets different parts of your design communicate with each other visually.
No custom JavaScript.
No complicated setup.
Just flexible, real interactions.
Usage Examples for Every Action Type
Here are real, practical examples of how each action can be used in your designs.
Show hidden content when clicking a “Read More” or “Details” button.
Hide a banner, notice, or message when clicking a close icon.
Toggle an expandable FAQ section or dropdown-style content area.
Add a class on hover to highlight a card or activate a custom CSS animation.
Remove a class to reset styling when the user moves the mouse away.
Toggle a class to open or collapse a sidebar, change button states, or switch themes.
Open an Elementor popup using your own custom trigger instead of a preset button.
Close an Elementor popup automatically when another element is clicked.
Toggle an Elementor popup to create your own open/close popup button.
Move to the next item inside a connected slider or carousel using a custom-designed arrow.
Move to the previous item with your own navigation button or icon.
Jump to a specific item inside a gallery or slider using dots, numbers, or thumbnails.
Open a UE Simple Popup for lightweight announcements or quick info panels.
Close a UE Simple Popup when clicking any element you choose.
Toggle a UE Simple Popup open or closed with the same trigger.
What This Widget Adds to Your Workflow
Build micro-interactions visually
Make elements respond to user behavior
Create custom toggles and navigations
Connect multiple widgets intelligently
Add dynamic behavior to any layout
Personalize sections based on date/time rules
Use classes for advanced CSS styling
Control parts of the page that normally require custom JS
It’s a new layer of interaction inside your existing workflow, simple, intuitive, and extremely flexible.
Final Thoughts
The Conditions Widget was created to give designers and site builders an easier way to add dynamic behavior to their Elementor pages. Our team built it based on real user feedback, real use cases, and real needs.
It brings a new level of control, flexibility, and creativity, without code, and without replacing any existing Elementor features.
And this is only the start. We’re continuing to expand the widget based on what our community requests next.
If you have ideas for new triggers or new actions, we’d love to hear them.
