Plugins › UpdraftPlus
Back up WordPress from chat.
Inspect backup coverage and create local database or content-file backups from ChatGPT or Claude.
Tested by us on 31 October 2026 with UpdraftPlus Free 1.26.14, from ChatGPT and Claude. Requires AI Puffer 2.5.22 or later, UpdraftPlus 1.26.14 or later, single-site WordPress 6.9 or later with the Abilities API, and a connected user allowed to manage UpdraftPlus. Premium extensions are outside this tested scope.
Things to ask
- “Check my recent backup coverage.”See the history total, inspected sample and local components.
- “Back up my database before a change.”Follow the same job until native completion is confirmed.
- “Back up my database and content files.”Check requested coverage, local files and warnings before proceeding.
Recipes
Integration actions
Actions used by this integration and their test status. At Trusted, supported changes follow the connected WordPress user’s permissions.
| What your assistant uses | What it does | At Standard | Checked |
|---|---|---|---|
ai-puffer/updraftplus-status | Read current backup scope and cron status | Reads | Tested |
ai-puffer/updraftplus-list-backups | Inspect recent backup sets and local file counts | Reads | Tested |
ai-puffer/updraftplus-get-backup | Check a known job for completion and coverage | Reads | Tested |
ai-puffer/updraftplus-create-backup | Queue a local database or content backup | Asks you | Tested |
Before you start
Use AI Puffer 2.5.22 or later, UpdraftPlus 1.26.14 or later and WordPress 6.9 or later with the Abilities API. Single-site WordPress only. Connect with a WordPress user allowed to manage UpdraftPlus. This tested integration uses UpdraftPlus Free’s native PHP engine; no Premium WP-CLI feature or extra adapter plugin is needed.
What you can ask
- Check recent backup sets and their local components.
- Back up the WordPress database.
- Back up the configured content files.
- Back up both before considering a site change.
Read-only inspection reports a bounded sample and matching history count. A history entry is not proof of successful completion, remote availability or a tested restore.
Creation and completion
Your assistant reads current settings and queues one backup. It follows the returned job ID to check completion. Queued is not completed. WordPress cron must run and the server needs sufficient disk space. If automatic cron is disabled, your host needs a separate cron runner. Missing components, warnings or an uncertain result need review before any dependent change.
Backups contain the requested WordPress database and configured content components: plugins, themes, uploads, must-use plugins and other wp-content files. Native exclusions remain in effect. WordPress core, wp-config.php, additional databases and other hosting files are outside this scope. An excluded or empty component may have no archive.
These jobs create local archives only. They do not upload remotely, send a backup report email or prune older backups. The new set is kept until you remove it in UpdraftPlus. Other native jobs and saved settings retain their behavior. A local backup stays on the same host; it does not replace an off-site copy or restore test.
Permissions and plans
Inspection works at Read only, Standard and Trusted within the connected user’s native UpdraftPlus permissions. Creating a backup requires WordPress approval at Standard; Trusted follows the chosen policy. All AI Puffer plans use normal website actions, without AI Puffer AI credits. UpdraftPlus Premium extensions and remote storage are outside this tested scope.
Recovery and limits
After an uncertain response, inspect the original operation and known job ID before requesting another backup. The worker rechecks access before starting. Once the native engine has started, use UpdraftPlus to stop it; disconnecting chat does not cancel native resumptions. The assistant returns metadata and counts, not raw archives, database contents, private paths, download links or storage credentials. Restore, deletion, downloads, migrations, schedule/storage changes and retention settings stay in UpdraftPlus’s own WordPress screens.