Plugin Configuration

Connect the Tapeto plugin to your account and understand what it does when it receives a push.

After activating the plugin, go to WP Converter → Settings in your WordPress admin (requires the manage_options capability).

Connect the plugin

In your Tapeto account, add a new WordPress connection for this site and copy the secret key it generates.
In the plugin settings screen, paste the secret key into the Secret Key field and save.
Back in Tapeto, run a test push from any completed conversion to confirm the connection works.

Why a secret key, not a password

Every request from Tapeto’s API to your site is signed with HMAC-SHA256 using this secret key. Your site verifies the signature before accepting any content, so the key never has to be sent on every request and isn’t usable on its own without the matching request.

What the plugin does on push

The plugin exposes a few internal REST routes under /wp-json/wp-converter/v1/, all of which require a valid HMAC signature:

scaffold — creates the initial site structure: pages, menus, and (on Agency/Studio) custom post types and taxonomies.
gutenberg-content — injects WordPress block grammar into an existing page’s content, looked up by slug.
elementor-content — injects Elementor JSON into an existing page, looked up by slug, and writes the required Elementor post meta (_elementor_data, _elementor_edit_mode, _elementor_version, _elementor_page_settings, _elementor_css).

Gutenberg content is registered as a custom block (tapeto/html-block); Elementor content is registered as a widget in its own “Tapeto” category. Both use a small template engine to substitute {{ variable }} placeholders when rendering.

Supported builders

Today the plugin can receive Gutenberg and Elementor content. Oxygen, Divi and Bricks conversions can still be generated and exported as JSON or WXR, but the plugin doesn’t yet expose endpoints to push them directly — see Exporting Results for the alternative.