CloseHub Connector
Connect your WordPress site to CloseHub with a single API key in order to send statistics.
Will this break my store?
What the WordPress.org registry says about keeping CloseHub Connector running.
Tested to 7.0.2
Tested against the WordPress branch in use today.29 days ago
8.1
Your host must be running at least this version.6.4
2
Maintenance & trust
Scored on how CloseHub Connector is looked after — not on how many stores run it.
Maintenance
35 / 35WordPress compatibility
20 / 20Support responsiveness
Not enough dataMerchant satisfaction
Not enough dataListing transparency
6 / 10Ratings
No one has rated this plugin on WordPress.org yet. That is a statement about the ratings page, not about the plugin — plenty of well-kept plugins never collect them.
CloseHub Connector replaces the multiple credentials previously required to link a WordPress site with CloseHub — a marketing project management platform.
Once the plugin is activated, it generates a secure API key and exposes a dedicated REST API namespace (/wp-json/closehub/v1/) that CloseHub uses to interact with your site.
What it replaces:
- WordPress Application Password (username + password)
- WooCommerce REST API consumer key and consumer secret
- Gravity Forms API key
You only need to share two things with CloseHub:
- Your site URL
- The generated API key (found at Settings → CloseHub)
Available endpoints:
GET /closehub/v1/ping— verify the connectionPOST /closehub/v1/posts— publish or draft a postGET /closehub/v1/woocommerce/orders— fetch order data (requires WooCommerce)GET /closehub/v1/gravity-forms/forms— list forms (requires Gravity Forms)GET /closehub/v1/gravity-forms/forms/{id}— get form detailsGET /closehub/v1/gravity-forms/forms/{id}/entries— count form entries by date range
WooCommerce and Gravity Forms endpoints return a clear error if those plugins are not active — they are not required.
Multisite networks:
On a WordPress Multisite network, the same endpoints listed above are shared by every site in the network — there is no separate namespace or key to manage. Activate the plugin network-wide and go to Network Admin → Settings → CloseHub to find one API key shared by the whole network. Every request to those endpoints automatically returns a sites array with one entry per site in the network (site_id, url, and that site’s data or an error message), instead of a single site’s result — handy when a network is used to run the same company in multiple languages.
Go to Settings → CloseHub in your WordPress admin. The key is displayed there along with a copy button.
Yes. Click Regenerate Key on the Settings → CloseHub page. The old key stops working immediately — update CloseHub with the new key right away.
No. Both are optional. If they are not active, those endpoints return a 503 response with a clear message instead of crashing.
The key is stored in wp_options (or network-wide in wp_sitemeta on multisite), never exposed on the frontend, transmitted only via HTTPS, and verified using constant-time comparison (hash_equals) to prevent timing attacks. It is never logged or included in REST responses.
Yes. When network-activated, the plugin generates one API key shared by every site in the network (managed from Network Admin → Settings → CloseHub instead of a per-site Settings page), and the same REST endpoints automatically query every site and return combined, per-site results. On a regular, non-multisite install, everything works exactly as a single site as described above.
No. It integrates with those plugins using their public PHP APIs but is not developed, endorsed, or supported by WooCommerce or Gravity Forms.
Plugin details
Tags on WordPress.org