Both. The free Uncanny Automator already stores recipes in uo-recipe and runs in automator_recipe_logs, so SleekAI can read them whether or not Pro is active. Pro features like advanced webhooks, premium integrations, and unlimited apps simply give the bot more data to read when those triggers and actions exist on recipes.

The Wizard exposes the uo-recipe custom post type, its triggers and actions postmeta, automator_recipe_logs, automator_recipe_log_meta, and automator_action_logs. You can map any other Automator option or table in two clicks, including custom triggers from third-party Automator integrations.

By default no. SleekAI is read-only. Action toolcalls are opt-in and disabled. The bot identifies which recipe needs attention, but the actual pause or run step is still a manual admin click in the Automator UI, which keeps the audit trail clean for operational tooling that runs critical business logic.

Yes. Tokens are stored inside recipe step config. The bot can quote which tokens a recipe uses, which steps reference them, and where a missing or unresolved token broke a run. Loop steps are exposed similarly, so the bot can explain why a loop iterated 17 times when it was supposed to iterate 3.

No. SleekAI maps only the data the Wizard explicitly exposes. Integration API keys live in their own options that are usually obscured. You can choose to map only metadata like integration name and last error, which is enough for diagnostics, while leaving credentials untouched in the database.

Yes. The bot reads each step's trigger or action type, the integration, and the configuration, then narrates the recipe as a sequence of plain English steps. That is useful for handing a site to a new team member who needs to understand the automation stack quickly.

Yes. Anonymous recipes are recorded the same way in the logs. The bot can quote how many anonymous users a recipe processed in a period and how many succeeded or failed, which matters for marketing automations that target site visitors rather than logged-in members.

Yes. Display conditions support user role, logged-in state, and URL pattern. A typical setup limits the operations bot to administrators on /wp-admin/admin.php?page=uncanny-automator. A separate marketing-facing bot can answer non-sensitive automation summary questions under multibot.