TBC - Web - Automations

v1.1.5 Show changelog

Changelog · v1.1.5 ×

1.1.5 — 2026-09-03

🛠 Fixed

• A "create post" action the site refuses fails that one action, not the whole run. Fluent Community throws, rather than answering, when a post is empty, over the site's length limit or missing a title the community requires — and an automation whose post hit one of those stopped dead mid-run, taking every later action with it. The refusal is caught now and recorded against the action; the rest of the run carries on.

1.1.4 — 2026-08-26

🔧 Changed

• The shared admin library caught up with the rest of the suite. Every TBC plugin ships a byte-identical copy of the same admin CSS, JS and licenser under one handle, and this plugin's copy had fallen behind. It now carries the Hide sensitive control — which covers credentials on screen so a settings page can be screen-shared or screenshotted without publishing them — the one-open-at-a-time accordion, and newest-wins registration, so the copy WordPress actually loads is the most recent one installed rather than whichever plugin happened to register first.
• The documentation theme re-synced, so this plugin's HTML reference looks like the rest of the suite again.

1.1.3 — 2026-08-01

🔧 Changed

• The License tab's support contact follows the site's vendor identity. A dev-bundle buyer running managed service for their own clients points it at their own business from the client site's wp-config.php, so their clients see their address rather than ours. Left undefined it stays Two Birds Code, so nothing changes on an ordinary install.

1.1.2 — 2026-07-29

🛠 Fixed

• A notification sent by a recipe could blank the whole notification list. Fluent Community's portal reads a route on every notification outside its own comment and mention types, so a row saved without one throws — and because the list renders as a single loop, one bad row takes out every notification for every member. The unread badge and pagination keep reporting correct totals, so it reads as "notifications stopped being recorded" against a database that's completely intact, and deactivating the plugin doesn't help because the row is already written. Recipes that left the notification's link empty were saving exactly that. They now fall back to a sensible route.
• Licensing resilience. A rate limit or brief license-server hiccup no longer disables a licensed site — the plugin runs on its last good check, and only a definitive invalid or expired answer gates features. A revoked key also can't slip back to licensed between checks.

1.1.0 — 2026-07-09

✨ New

• A "Delete data on uninstall" switch on the License tab. Automations has no separate settings tab, so the standard Data Management toggle lives on the License panel. Off by default: uninstalling leaves your stored settings alone unless you turn it on. Nothing about your recipes or activation is touched.

🔧 Changed

• Uninstalling no longer throws away your license key, and only clears data when you ask. Previously removal always deleted the key and caches. Now uninstall does nothing unless you opt in with the toggle above — and even then the key is deliberately kept, so a rebuild, migration or reinstall won't force re-activation. Opting in removes only the plugin's own caches, warning flags, legacy migration markers and the toggle setting.
• The Automations admin screen follows the shared TBC palette, rewired from baked-in light-only colors to the shared design tokens, so it renders consistently with the rest of your TBC admin including dark admin schemes. No settings or behavior change.

📡 Internal

• Resynced the bundled licenser to the canonical version, keeping every plugin's copy byte-identical under the release drift gate. It picks up a license-nag suppression option other plugins use for pre-purchase pages; Automations doesn't use it, so runtime behavior is unchanged.

1.0.1 — 2026-06-30

🛠 Fixed

• Your automations run again under the latest Uncanny Automator. After a recent Automator update every TBC trigger and action went silent — direct messages, follows and unfollows, in-app notifications and the custom-profile-field trigger all sat greyed out at "Not completed" with "The plugin for this action is not active", even though native WordPress and Fluent Community steps in the same recipe kept completing. Automator's new runner only executes an action once its integration is on the active list, and the suite registered its two groups without marking them active. Each is now a first-class Automator integration, marked active whenever its dependency is present, so existing recipes fire again with no edits. Integration, action, trigger, meta and token codes are all preserved.

📡 Internal

• Integration registration moved onto Automator's canonical base-class pattern — each product group is now an Integration subclass registered on the automator_add_integration hook, loading the triggers and actions it owns. This drops the hand-rolled registration that leaned on Automator internals, so the suite is far less likely to break on future Automator updates.

1.0.0

Initial release.

✨ New

• Four standalone TBC Automator add-ons consolidated into one licensed suite — Send Message (FluentChat DM), Send Notification, Follow / Unfollow, and Custom Field Triggers.
• Automations grouped by target product in Automator's picker — TBC – Fluent Community and TBC – FluentChat — each with its own icon, registered only when its dependency is active so empty groups never show. A one-time migration re-homes any recipe built under the old single integration; recipes resolve by code, so none break.
• The standard TBC licenser and auto-updater, with the license panel under TBC Community App → Automations.
• Every trigger and action modernized onto Uncanny Automator's base-class API so new automations drop in cleanly. Behavior is unchanged and all codes are preserved, so recipes keep working after switching from the four old plugins.
• Each automation loads only when its dependency is present, so missing dependencies are skipped rather than erroring.

Gamification triggers — all on real Fluent Community hooks, no polling:

• Receiver-side, rewarding the author whose content earned engagement, which Fluent Community's own integration doesn't provide: a post receives a reaction (plus total received), a comment receives a reaction, a post receives a comment, and a user gains a follower (plus total followers, Pro).
• Actor-side, rewarding the user who engaged: publishing a post, writing a comment (with is-reply), following someone, reacting to a post, and reacting to a comment — each with a running-count token, so one recipe handles the first, the Nth or every occurrence without dedicated triggers. These cover free-Automator and global scope, complementing Fluent Community's space-scoped Pro equivalents rather than duplicating them.
• Plus user promoted to moderator or admin, and adds or updates a social link. Avatar and cover-photo triggers were considered but Fluent Community's inline media endpoint fires no usable hook, so they're omitted rather than faked with polling.
• BuddyBoss-style follow-request and join-request triggers are deliberately omitted — Fluent Community has no hook or concept for them.

Remaining BuddyBoss-gap automations, built on Fluent Community's own models so its hooks fire and chain:

• Actions: create a space, publish a post as a user, set a custom profile field without a trigger loop, and email all active members of a space.
• Triggers: a user sends or receives a 1-to-1 direct message, and a user sends a group or space message. FluentChat exposes no reaction hook, so a chat-message reaction trigger is omitted.
• Still unsupported by Fluent Community and therefore absent: duplicates of space create/enroll/remove already in its stock integration, forums, points and ranks, profile types, and email invitations.

Automations · WordPress plugin · Uncanny Automator

The Fluent Community blocks Automator is missing.

“When a member gets their tenth reaction, award a badge.” “When someone joins, send a welcome DM.” Eighteen triggers and actions built on Fluent Community’s own models and hooks — so the results are identical to doing it by hand. No code, no glue plugins.

18triggers and actions, under one integration in Automator

0polling — real Fluent Community hooks, never a timer

1integration to find them all: “TBC Automations”

↻they chain — a published post can fire your reaction and comment rewards

Three groups · eighteen blocks

Messaging, gamification, and the rest.

Click a tab. The capture opens full size.

Automations › What is inside Included

Choose a view

Messaging & follows Gamification Profiles & spaces

Reach a member directly

DMs, notifications and follows

• Send a direct message through FluentChat
• Send an in-app notification — with mobile push and an optional tap-to-open destination: a space, post, profile, course or lesson
• Triggers on messages — a user sends one, or receives one
• Follow and unfollow a user as an action
• A user gains a follower — with a running follower-count token, so “reach 100 followers” is one recipe

Close

Built for GamiPress and points engines

Reward what people actually do

Several of these carry a running total as a token, which is what turns a trigger into a milestone.

• A user’s post receives a reaction — with a total-reactions token, so “get 10 reactions → badge” works
• A user’s comment receives a reaction
• A user’s post receives a comment
• A user publishes their first post, or writes their first comment
• A user is promoted to moderator or admin

screenshot coming soonstore-assets/products/tbc-automations/recipe-gamification.webp

Profiles, spaces and content

Act on the community itself

• A user updates a custom profile field to a specific value — as a trigger
• Set a user’s custom profile field — as an action
• Create a space, public, private or secret
• Publish a post as a user, to a space or the main feed
• Email all members of a space

screenshot coming soonstore-assets/products/tbc-automations/recipe-content.webp

Smart by design

• Loads only what you have — each automation activates when its dependency is present, so nothing errors on a feature you have not installed
• No loops, no hacks — real Fluent Community hooks rather than polling
• Where Fluent Community has no hook for something, such as follow requests, it is left out rather than faked
• Auto-updating — activate your key and updates arrive through your dashboard

What you need

• Uncanny Automator (free or Pro)
• Fluent Community — Pro for follows, the gains-a-follower trigger and custom-profile-field automations
• FluentChat for the direct-message action and the send/receive triggers

Pricing

Free.

Automations is one of our free tools. Activate a licence key so updates arrive automatically, and build whatever recipes you like.

AutomationsWordPress plugin · Uncanny Automator integrationFree

At checkout$0