Summix

Sequensy lets you automate repetitive tasks on your WordPress site by building visual workflows. When something happens (a trigger), Sequensy runs a series of actions — creating posts, updating orders, syncing subscribers to your email platform, and more.
<h4>Build Workflows Visually</h4>
Design automation workflows on a visual canvas. Connect a trigger to one or more actions, configure each step with a simple form, and publish. No code, no cron jobs to manage, no third-party automation platform required — everything runs inside WordPress.
<h4>WordPress Triggers</h4>
Start workflows when key events happen on your site:
<ul>
<li>Post Published — fires when any post type is published</li>
<li>User Registration — fires when a new user account is created</li>
<li>User Profile Updated — fires when a user’s profile information changes</li>
<li>Comment Submitted — fires when a new comment is posted</li>
</ul>
<h4>WooCommerce Triggers</h4>
Automate your store with triggers for order events:
<ul>
<li>New Order — fires when a customer places an order</li>
<li>Order Completed — fires when an order is marked complete</li>
</ul>
<h4>WordPress Actions</h4>
Perform tasks on your site automatically:
<ul>
<li>Create Post — create a new post, page, or custom post type</li>
<li>Update Post — update the title, content, or status of an existing post</li>
<li>Create User — register a new WordPress user account</li>
</ul>
<h4>WooCommerce Actions</h4>
Manage your store without manual work:
<ul>
<li>Update Order Status — change an order to processing, completed, on-hold, etc.</li>
<li>Add Order Note — append a note to an order (customer-visible or internal)</li>
<li>Create Coupon — generate a coupon code with a specified discount type and amount</li>
</ul>
<h4>Third-Party Integrations</h4>
Connect workflows to external services you already use:
<ul>
<li>Kit (ConvertKit) — create subscribers, add tags, and remove tags to manage your email audience</li>
<li>Notion — create database entries to log data from your WordPress site</li>
<li>Campaign Monitor — add, update, and remove subscribers from your mailing lists</li>
</ul>
<h4>Features</h4>
<ul>
<li>Visual Workflow Builder — point-and-click canvas with a clear trigger → action flow</li>
<li>Conditional Filters — run actions only when specific conditions are met (e.g., post type is “product”, user role is “subscriber”)</li>
<li>Variable Substitution — pass data between steps using <code>{{Trigger.field}}</code> and <code>{{action_id.field}}</code> syntax</li>
<li>Activity Log — see a timeline of every workflow execution with status, duration, and error details</li>
<li>Async Execution — workflows run in the background via Action Scheduler so your site stays fast</li>
<li>Modular Packages — each integration is a self-contained package you can activate or deactivate independently</li>
</ul>
<h4>External Services</h4>
Sequensy can connect to third-party services to extend your workflow automation capabilities. Data is only sent to these services when you explicitly connect your account AND create a workflow that uses the service. You have complete control over what data is sent and when.
No data is sent to Sequensy or Summix servers. All workflow data is stored locally in your WordPress database.
Kit (ConvertKit)
Email marketing platform for creators. Sequensy uses the Kit API to create subscribers and manage tags on your Kit account.
What Data Is Sent: Email address, first name, and any custom fields you configure in your workflow actions. 
When Data Is Sent: Only when a workflow executes a Kit action (create subscriber, add tag, remove tag).
<a href="https://kit.com/terms" rel="nofollow ugc">Terms of Service</a> 
<a href="https://kit.com/privacy" rel="nofollow ugc">Privacy Policy</a>
Campaign Monitor
Email marketing platform for subscriber management. Sequensy uses the Campaign Monitor API to add, update, and remove subscribers on your lists.
What Data Is Sent: Email address, name, mobile number, custom fields, and consent to track preferences you configure in your workflow actions. 
When Data Is Sent: Only when a workflow executes a Campaign Monitor action (add subscriber, update subscriber, remove subscriber).
<a href="https://www.campaignmonitor.com/policies/#terms" rel="nofollow ugc">Terms of Service</a> 
<a href="https://www.campaignmonitor.com/policies/#privacy-policy" rel="nofollow ugc">Privacy Policy</a>
Notion
Collaborative workspace and documentation platform. Sequensy uses the Notion API to create entries in your Notion databases.
What Data Is Sent: User-configured properties and content as defined in your workflow actions (can include text, numbers, dates, etc.). 
When Data Is Sent: Only when a workflow executes a Notion action (create database entry).
<a href="https://www.notion.so/terms" rel="nofollow ugc">Terms of Service</a> 
<a href="https://www.notion.com/trust/privacy-policy" rel="nofollow ugc">Privacy Policy</a>
<h4>Privacy</h4>
Sequensy can connect to third-party services when you configure integrations. For complete details about what data is sent to each service and when, see the “External Services” section above.
No data is sent to Sequensy or Summix servers. All workflow data is stored locally in your WordPress database.
<h3>Development</h3>
<h4>Source Code</h4>
The uncompiled JavaScript/TypeScript source code is included in the <code>admin/src/</code> directory within this plugin.
The admin interface is built with React and TypeScript using Vite. To rebuild from source:
<ol>
<li>Navigate to the <code>admin/</code> directory</li>
<li>Run <code>npm install</code> to install dependencies</li>
<li>Run <code>npm run build</code> to compile assets</li>
</ol>
<h4>Build Tools Used</h4>
<ul>
<li>Vite (build tool)</li>
<li>React 18 (UI framework)</li>
<li>TypeScript (type-safe JavaScript)</li>
<li>Tailwind CSS (styling)</li>
</ul>

Sequensy

Build visual workflows that automate WordPress tasks — connect triggers to actions with zero code.

dudaster

Ele Conditions for Elementor turns static Elementor elements into interactive, context-aware components — without writing a single line of code.
There are two independent systems, both accessible from the Advanced tab of any widget, section, or container:
<h4>⚡ Triggers & Actions (client-side, no page reload)</h4>
Attach one or more trigger → action pairs to any element.
10 trigger types:
<ul>
<li>Click — user clicks the element</li>
<li>Hover — user hovers over the element</li>
<li>Delay on load — fires after X milliseconds from page load</li>
<li>Scroll into view — fires once when the element enters the viewport</li>
<li>Time on page — fires after X seconds the visitor has been on the page</li>
<li>Exit intent — fires when the cursor moves toward closing the tab</li>
<li>First visit — fires only on the visitor’s very first page load (localStorage)</li>
<li>Nth visit — fires on the Nth page load (visit counter in localStorage)</li>
<li>A/B Group A / B — fires for visitors randomly assigned to group A or B (persists via localStorage)</li>
</ul>
9 action types:
<ul>
<li>Show — make the target element visible</li>
<li>Hide — hide the target element</li>
<li>Toggle — toggle visibility on each trigger</li>
<li>Add / Remove / Toggle Class — apply a CSS class (great for CSS animations)</li>
<li>Scroll To — smooth-scroll the page to the target element</li>
<li>Focus — set browser focus on the target (input fields, etc.)</li>
<li>Close Others in Group — hide all siblings sharing a CSS class (accordion pattern)</li>
</ul>
Target selector: leave empty to act on the element itself, or enter any CSS selector to act on another element anywhere on the page.
Hide Initially: a dedicated switcher that hides the element on load independently of triggers — useful for elements revealed by a trigger.
<h4>🎛 Display Conditions (server-side, evaluated at render time)</h4>
Show or hide elements based on variables, rules, and time windows. Multiple conditions per element with AND / OR logic.
Built-in variables include: <code>user_role</code>, <code>is_logged_in</code>, <code>user_id</code>, <code>post_type</code>, <code>post_status</code>, <code>post_age_days</code>, <code>post_word_count</code>, <code>post_has_thumbnail</code>, <code>cart_count</code>, <code>cart_total</code>, <code>current_hour</code>, <code>current_day</code>, <code>current_month</code>, <code>current_year</code>, <code>utm_source</code>, <code>utm_medium</code>, <code>utm_campaign</code>, <code>utm_content</code>, <code>utm_term</code>, and more.
Condition types:
<ul>
<li>Simple — compare a variable to a value using ==, !=, >, <, >=, <=, contains, starts_with, ends_with, empty, not_empty</li>
<li>Time interval — show element only between two times of day (supports cross-midnight ranges)</li>
<li>Date/datetime interval — show element only within a date or datetime window</li>
</ul>
Custom variables — register your own variables via the <code>eleconditions_vars</code> filter in your theme’s <code>functions.php</code>.
ACF support — pick any ACF field from a searchable dropdown; the value is fetched at render time.
User meta — condition on any WordPress user meta key for the current visitor.
Debug mode — shows a red-bordered overlay with the evaluated variable values, visible only to editors and administrators.
<h4>Developer-friendly</h4>
<ul>
<li>Zero dependencies beyond Elementor</li>
<li>Fully filterable variable system</li>
<li>No inline styles injected into saved content — everything is evaluated at render</li>
</ul>
Note: Requires the free <a href="https://wordpress.org/plugins/elementor/" rel="ugc">Elementor</a> plugin.

Ele Conditions for Elementor

Add interactive triggers and conditional display logic to any Elementor element — show, hide, toggle on click, scroll, exit intent, and more.

Sequensy vs Ele Conditions for Elementor