Connect a WordPress Site

Outcome

You will connect a self-hosted WordPress site to TMXIO using the current plugin workflow and confirm that the connection is healthy on both sides. By the time you finish this page, the site should appear in TMXIO, the plugin should show a connected state in WordPress admin, and you should be able to run a manual Test Connection without an error.

This guide covers the modern connection path only. If your team has older internal notes referencing a “workspace token” as the primary connection step, treat those notes as legacy. The current plugin centers on a TMXIO account plus an API key, not a token paste.

Prerequisites

Before you start, make sure all of the following are true:

• You have WordPress admin access on the site you are connecting. Editor and contributor roles are not enough; the plugin’s settings live under the admin area.
• You can sign into the correct TMXIO workspace, or you have someone available who can. The plugin will refuse to save a connection that points at a workspace you cannot reach.
• The TMXIO WordPress Plugin is installed and active on the site. If it is not yet installed, follow Install and Connect first and return here once the plugin is showing up in the admin menu.
• The site has outbound HTTPS access to TMXIO. Most production WordPress hosts have this by default. Locked-down corporate or air-gapped environments may need explicit firewall allowances.

Note

If you are unsure which TMXIO workspace the site belongs in, stop and confirm with your account owner before you save the connection. Moving a site between workspaces after the fact is possible but adds an extra round trip with support.

Connecting the Site

1. Open the TMXIO plugin in WordPress admin.

   Sign into WordPress as an administrator and look for the TMXIO entry in the left-hand admin menu. The current plugin experience is built around connecting with a TMXIO account or an API key, not around pasting a workspace token as the primary path.

   If the plugin menu is not visible, confirm under Plugins that the TMXIO WordPress Plugin is installed and activated. A deactivated plugin will not render its admin pages.

2. Choose how you want to connect.

   The plugin gives you two main connection paths:

   • Create a TMXIO account from WordPress. Use this when the person setting up the site does not yet have a TMXIO login. The plugin walks you through account creation and then links the new account to the site automatically.
   • Enter an existing TMXIO API key. Use this when the account already exists and the person doing the WordPress install has been given an API key. This is the common path for agencies and managed hosting teams.

   If your TMXIO account can access more than one workspace, the plugin may ask you to pick the workspace before it saves the connection. Choose the workspace this WordPress site should belong to. The choice is recorded server-side and used for all subsequent reporting on this site.

   Behind HTTP auth?

   If your site is served from behind HTTP Basic Auth (for example a staging environment using .htpasswd, or a Cloudflare Access policy), TMXIO will not be able to reach /wp-json/ for validation. Either whitelist TMXIO’s outbound addresses, or temporarily relax the auth wall in front of /wp-json/tmxio/ while you complete the connection. Re-enable it afterwards if needed.

3. Save the connection and confirm.

   Click Save (or the equivalent confirmation button shown by the plugin). The plugin will validate the credentials against TMXIO before it persists the connection, so a save that returns without an error already implies a successful round trip.

   After saving, the plugin should switch to a connected state, the site should appear in the chosen TMXIO workspace, and the Test Connection action should succeed.

What Success Looks Like

A correctly connected site will show all of the following at the same time:

• The WordPress admin page for the TMXIO plugin reports the site as connected and shows the linked account context.
• TMXIO lists the site in the expected workspace, with a recent last-seen timestamp.
• You can use the plugin’s Test Connection action without an error and without retrying.

If only one or two of these are true, the connection is in a partial state and is worth investigating before you walk away from the site. Partial states tend to surface later as “disconnected” alerts in TMXIO even though the WordPress side looks fine.

After You Are Connected

Once the site is connected you can enable optional features such as Error Monitoring and 1-Click Access from the plugin’s settings page. See Common Tasks for the everyday plugin jobs and Heartbeat and Status for how TMXIO keeps track of the site over time.

Related Troubleshooting

• If the site is behind HTTP authentication, make sure the plugin can still reach TMXIO normally. See the HTTP Auth tab in External Troubleshooting.
• If the connection fails after a save, continue to External Troubleshooting or the plugin-specific Install and Connect guide.
• If the site connects but immediately reports as disconnected in TMXIO, the heartbeat path is failing rather than the initial credential exchange. See Heartbeat and Status.