WordPress Connector
Use tropikal-ai/connect-wordpress when the website runs WordPress and should
connect through a normal plugin job.
Requirements
- PHP 8.2 or newer.
- WordPress 6.x.
- Administrator access to
wp-admin. - Composer for source or Bedrock-style installs.
Install as a Plugin Folder
Place the plugin in the WordPress plugin directory:
cd wp-content/pluginsgit clone https://github.com/tropikal-ai/connect-wordpress.git tropikal-connect-wordpresscd tropikal-connect-wordpresscomposer install --no-dev --optimize-autoloaderThen activate TROPIKAL Connect for WordPress in wp-admin.
Install with Composer or Bedrock
composer require tropikal-ai/connect-wordpress:^0.1Activate the plugin through the WordPress admin screen or your normal deployment process.
Connect the Site
- Open
Settings -> TROPIKAL Connect. - Confirm the site identity.
- Click Connect.
- Return to the plugin page after setup completes.
The plugin keeps private setup state server-side and never prints private credentials in admin HTML.
Grant Connected Data
The plugin discovers safe WordPress business objects:
- Posts.
- Pages.
- Media.
- Public custom post types where safe.
Each object has independent grants:
- Read: list, search, and read approved fields.
- Write: create drafts, update drafts, and publish approved content.
- Delete: move approved objects to trash when Delete is explicitly enabled.
Write does not include Delete. Empty grants expose nothing.
After changing grants, return to TROPIKAL and click Sync Connected Data.
Add Website Chat or Booking
After the site is connected, click Add Job on the TROPIKAL Connect admin page. Choose Chat or Booking and complete the central setup.
Chat loads automatically on connected public pages only while its Job binding
is active. Place Booking where it belongs using the TROPIKAL Booking block
or [tropikal_booking] shortcode.
Safe Content Behavior
New content is created as a draft. Updating already published content should use a draft or approval flow rather than silently changing live pages. Publishing requires explicit approval metadata from TROPIKAL.
Private post meta, user emails, authentication data, sessions, and secret-shaped fields are not exposed by default.