One library.
Every connected site.
Connect WordPress with a revocable key. Generate and browse static previews in WP Admin, then review and export in the web app for manual installation.
Authentication
Bearer connector key
Transport
HTTPS / JSON
Current scope
Generate, browse, preview
Account library
1
Shared by the app and connector
Builders
2
Elementor and WPBakery
Active keys
1 / 5 / 10
Free / Starter / Pro
Connection flow
Account to site, without a WordPress password.
Execution boundary
The WordPress.org connector generates and displays library metadata and static previews. It does not download, install, activate, or execute generated add-on code.
Current workflow
What works where
The web app and WordPress.org connector share an account library, but they have different roles. These are the current supported paths, not promises about future or archived connector editions.
On a small screen, scroll the comparison horizontally.
| Task | Moduify web app | WordPress.org connector |
|---|---|---|
| Generate | Elementor and WPBakery studios; account and tokens required. | Submit generation jobs from WP Admin after connecting an account. |
| Preview | Design preview and source review; not a complete WordPress runtime. | Static design preview and library thumbnails; no generated PHP or preview JavaScript execution. |
| Library | Review saved account items and published examples. | Published catalog before connection; private account items after connection. |
| Export | Plugin ZIP export in the matching studio, subject to output checks. Public gallery downloads currently provide PHP source, not a plugin ZIP. | No generated-code downloads; continue in the Moduify web app. |
| Install | No remote installation. Export a ZIP, then upload it through WordPress Plugins manually. | Not supported. The connector does not write generated plugin files. |
| Activate | A WordPress administrator activates the uploaded add-on on the destination site. | Not supported for generated add-ons; activation is a separate manual WordPress action. |
| Direct push to a site | Not available. | Not available. |
Manual installation is separate
Review the result and its validation findings in Moduify, export a plugin ZIP from the matching studio, then upload and activate it manually on a staging WordPress site with the matching builder active.
Checks are not a compatibility guarantee
A compile pass covers only the automated checks listed for that output. It is not a full WordPress runtime, security, or theme/plugin compatibility audit. Review any findings and test on staging before production.
// setup sequence
Connect a site in four steps.
The account creates the credential. WordPress verifies the site. From then on, the connector works against the same generation history and token rules as the application.
Open connector settingsCreate a connector key
Open WordPress Connector in your Moduify dashboard. Name the key, create it, and copy it when it is shown.
Install the connector plugin
Install and activate Moduify AI Connector in WordPress, then open Moduify > Connection in WP Admin.
Verify the site
Paste the connector key and save. Moduify registers the site against your account without using your WordPress password.
Generate, review, export
Generate in WP Admin and review the static preview. Continue in the Moduify web app to edit, check, and export a ZIP; install and activate it manually in WordPress.
// shared library policy
The same add-ons, in both places.
Generation source does not create a second content silo. Private items stay with your Moduify account. WP Admin displays metadata and static previews; edit and export in the Moduify web app.
// api boundary
Only the data needed for the job.
The connector uses authenticated JSON requests to verify the site, submit generation work, check job status, and read the eligible library.
Connection verification
Site URL, site name, WordPress version, PHP version, and connector version identify and verify the installation.
Generation request
The selected builder, add-on name, prompt, and connected site ID enter the same generation pipeline as the web application.
Library response
Catalog and account items return with builder metadata, static preview URLs, and validation state. This connector does not retrieve installable source code.
// security and execution
Control stays with the account and site admin.
Keys are revocable
Active connector key limits follow your plan: one on Free, five on Starter/Standard, and ten on Pro. Every key remains revocable.
Secrets are one-time
A new key is displayed once. Moduify stores its hash for verification and never exposes the full secret again.
Requests stay server-side
The WordPress plugin sends authenticated HTTPS requests from the server. The connector does not require a browser-side secret.
Generated code stays out of the connector
The WordPress.org connector generates and displays library metadata and static previews. It does not download, install, activate, or execute generated add-on code.
// common questions
Before you connect.
The connector handles generation and static previews. Download and manual installation are separate steps outside this plugin.
Are WordPress-generated add-ons saved separately?
No. Connector generation is saved to the same user-owned Generated Items history used by the Moduify application, so both surfaces read from one account library.
Does selecting an item install or run its code?
The WordPress.org connector generates and displays library metadata and static previews. It does not download, install, activate, or execute generated add-on code.
Can the web app push directly to a remote WordPress site?
Direct deployment from the web app to a remote WordPress site is not available. Export from Moduify and install manually in WordPress; the WordPress.org connector is not an installer.
Does a passed check guarantee compatibility with my site?
A compile pass covers only the automated checks listed for that output. It is not a full WordPress runtime, security, or theme/plugin compatibility audit. Review any findings and test on staging before production.
// ready to connect