Uncanny Automator: Connecting Your Plugins

1 min read

Overview #

Uncanny Automator connects the plugins in your stack so they act as one system: when a form is submitted, a contact is created in FluentCRM; when a course is completed, an email is sent. It is the automation engine of the Xponent Stack, licensed by Xponent and included with your plan.

What’s Included #

  • Uncanny Automator Pro license: licensed by Xponent, included with your plan
  • Ready-made integrations: first-party triggers and actions for Fluent Forms, FluentCRM, TutorLMS, WooCommerce, and more
  • No code: recipes are built from triggers and actions, no snippets
  • Runs on your site: automations execute on your own infrastructure

What You Can Build (examples) #

Uncanny Automator is best understood through the flows it can run. Here are a few real examples, each of which we can build and test for you:

  • A form becomes a contact: when someone submits a Fluent Forms lead form, they’re created as a FluentCRM contact and added to your “Leads” list automatically.
  • A purchase triggers an email: when someone buys a product in WooCommerce, they’re added to a “Customers” list and sent a welcome or upsell email.
  • A course completion fires a follow-up: when a student finishes a TutorLMS lesson or course, they’re sent a certificate link or a “ready for the next course” email.
  • A registration opens a membership gate: when a new account is created, assign them a Wishlist Member level so they immediately see member-only content.

The pattern is the same every time: trigger → action, no code. But knowing which triggers to build, and wiring them so they don’t conflict, is where the value is.

Building Automations #

  • Describe the flow: “when someone buys product X, add them to this list and email a welcome” is a recipe we can build.
  • Request via support: send us the flow you want; we build and test it.
  • Review anytime: recipes are visible and editable in your admin.

Have Us Do It #

We configure Uncanny Automator to the Xponent standard and build automations around the exact plugins in your stack. If you’d rather we build the flow for you, describe it via a plugin activation request or support, and we’ll build and test it so it just works.

The Xponent Standard #

Practice Why
Self-hosted Automations run on your site: no cloud dependency
Stack-native Built around the exact plugins you already run
Built by us Recipes follow a consistent pattern: maintainable and debuggable
One engine Uncanny is the standard: no competing automation plugins

Related Articles #

Updated on August 31, 2026