Plugin support

Your assistant reaches plugins in two ways: through abilities that a plugin registers with WordPress (the Abilities API), and through a plugin’s REST API. Either way it works as the WordPress user you connected, and your safety level decides what happens without you.

We sort plugins into three groups. Tested by us: we ran the workflows ourselves, from ChatGPT and Claude, and wrote recipes. Next on our list: being tested next. Reachable: it shares abilities or a REST API, so it works in principle, but we haven’t tested it.

Tested by usWooCommerceProducts, stock, coupons, ordersTested by usYoast SEOSEO fields, scores, noindexTested by usACFCustom text fieldsTested by usWordPressPosts, pages, imagesTested by usElementorPages, templates, global stylesTested by usRedirectionRedirects, 301 and 302Tested by usDuplicatorBackups, before you change thingsTested by usCache pluginsClear the cache after a changeNext on our listRank MathAudits, scores, linksTested by usWPFormsCreate and edit formsReachableEasy Digital DownloadsOrders, customers, discountsReachableLifterLMSCourses, lessons, studentsReachableMemberPressMembers, subscriptionsReachableAll in One SEOSEO fields, auditsTested by usFluent FormsEntries and notificationsReachableCharitableCampaigns, donations

Routes and abilities that stay closed

Whatever the plugin, these routes and abilities aren’t offered: site and plugin settings, users and roles, installing plugins, and server and plugin files. Batch routes, which change many things in one request, are closed too. Settings, users, plugins and themes are handled by AI Puffer’s own WP-CLI commands instead, and theme files on paid plans only through a theme draft (see Themes).