# MightWork connector installation guides Canonical hub: https://mightwork.us/docs Never request credentials in chat. Use a password manager and the provider's credential fields. Do not claim marketplace availability or a successful connection without verifying it. # Install MightWork Leads for WooCommerce https://mightwork.us/docs/woocommerce Bring the contact from each new WooCommerce order into your MightWork Leads inbox. Download version 1.0.1 directly from MightWork. The WordPress.org listing is awaiting review. ## Requirements - A MightWork workspace owner with Leads Connector access. - A WordPress administrator on an HTTPS store with WordPress 6.5+, WooCommerce 9.0+ and PHP 7.4+. The plugin supports HPOS. - The plugin download is free. Your MightWork plan must include Leads Connector; no paid WooCommerce connector extension is required. ## 1. Upload and activate Download mightwork-leads.zip using the button below. Leave the file zipped. In WordPress, open Plugins → Add New Plugin → Upload Plugin. Choose the ZIP, select Install Now, then Activate Plugin. WooCommerce must already be active. Download plugin · 1.0.1: https://mightwork.us/downloads/mightwork-leads.zip ## 2. Create the connection In MightWork, select the workspace that should receive orders. Open Connections → Leads Connector. Choose WooCommerce, give the connection a recognizable name, enter the exact HTTPS Store URL shown in the WordPress plugin settings, and enter a new signing secret of at least 16 characters. Save the connection. Copy the inbound URL shown after saving. Keep the signing secret you entered in your password manager; MightWork will not display it again. Never include it in screenshots or chat. Open Leads Connector: https://app.mightwork.us/connections/leads ## 3. Save your connection Open WooCommerce → Settings → Integration → MightWork Leads. Paste the inbound URL and signing secret from the same MightWork connection. Enable the connection and save changes. The destination must start with https://app.mightwork.us/api/lead-connectors/inbound/. The secret field is blank after saving; this does not mean it was lost. Screenshot: https://mightwork.us/guides/woocommerce-settings.png ## 4. Check one new order Use the connected store's test-payment flow to create a new order with an email address you control. Do not charge a real customer to test installation. Open MightWork → Leads and find the matching contact with source WooCommerce. Check the email and order reference. An order without a usable email address is skipped; orders created before connection are not imported. Only the order reference and billing contact fields are sent. Payment details, purchased items and totals are not sent. An order does not grant marketing consent. Check your Leads inbox: https://app.mightwork.us/leads ## Troubleshooting ### The ZIP will not install Upload the plugin ZIP, not a source-code archive. Confirm WooCommerce is active and your server meets the requirements above. Ask your WordPress administrator if Upload Plugin is missing. ### Settings will not save Copy both values from the same connection. Use the exact HTTPS inbound URL, with no query string or trailing text. The signing secret must be at least 16 characters. Match the exact Store URL shown by the plugin, including www or any subdirectory. A staging store needs its own connection and endpoint. ### A new order did not appear Check that the connection is enabled in both apps, that the order has an email address, and that your MightWork plan includes Leads Connector. In WooCommerce → Settings → Advanced → Webhooks, inspect the MightWork webhook's delivery status. After fixing the cause, save the plugin settings to re-enable delivery, then create another test order. Missed orders are not replayed. Give support the order reference and time, never the secret. ### Rotate a secret or update the plugin To replace a signing secret, disconnect the old MightWork connection, create a new one with a new secret, then save both the new endpoint and secret in WooCommerce. For an update, download the new ZIP and use WordPress's upload-and-replace flow. Recheck one new test order afterward. ## Remove Pause by clearing Enable in the plugin settings and saving. Deactivating MightWork Leads removes its managed webhook and disables delivery. Deleting the plugin removes its settings, while WooCommerce orders and other plugins' webhooks remain. Previously imported MightWork leads remain until you delete them. Reactivation requires saving the secret again. # Connect Shopify to MightWork https://mightwork.us/docs/shopify Bring contacts from new Shopify orders into your selected MightWork workspace. Public Shopify App Store installation is not available yet. These instructions cover approved development-store testing until Shopify review is complete. ## Requirements - A MightWork workspace owner with Leads Connector access. - Permission to install apps on the Shopify store. During review, use an approved development store. - A store can belong to one MightWork workspace at a time. Select the right workspace before approving access. ## 1. Choose your workspace Sign in to MightWork and select the business that should receive the store's contacts. Open Connections → Leads Connector, then select Install the Shopify app or view customer data requests. The Shopify webhook option is a separate manual connection. Check the selected workspace before continuing. If another workspace already owns this store connection, contact support to resolve the binding. Open Shopify setup: https://app.mightwork.us/connections/shopify ## 2. Approve Shopify access Enter your permanent store domain, such as your-store.myshopify.com, without https:// or a path. Select Continue to Shopify. Sign in on Shopify and review the app permissions. Approve only for the intended store, then return to MightWork. A Shopify connected message confirms that the connection was saved. Screenshot: https://mightwork.us/guides/shopify-connect.png ## 3. Check a new order Create an order using Shopify's test-payment flow with an email address you control. Open MightWork → Leads and find the matching contact with source Shopify. Only new orders are imported. The app reads the order reference and contact name, email, phone and company when available. It does not import order items, totals or payment details, or subscribe the buyer to marketing. Check your Leads inbox: https://app.mightwork.us/leads ## 4. Know your privacy controls A Shopify customer data request appears in MightWork's Shopify screen for the workspace owner. Download the matching records and deliver them securely to the verified requester within 30 days. A download is not proof that the customer received the response. Signed customer deletion requests erase matching imported contacts. Shop deletion requests erase the shop's imported records after uninstall is verified. If Shopify cannot confirm the installation state, MightWork staff receive a durable verification task. View customer data requests: https://app.mightwork.us/connections/shopify ## Troubleshooting ### Shopify says the app cannot be installed Until public review is complete, installation is restricted to approved development stores. Do not purchase an unrelated extension to unlock this app. ### The connection did not complete Check the permanent myshopify.com domain and the selected MightWork workspace. Start the connection again from MightWork; an old callback link cannot complete a new installation. ### Orders stopped arriving Confirm the connection is enabled, the workspace still has Leads Connector access, and new orders include email addresses. Reconnect from MightWork if Shopify authorization expired. Report the store domain and order reference to support, without customer details or tokens. ## Remove Pause or disconnect in MightWork → Connections → Leads Connector to stop imports. To uninstall, remove MightWork Leads in Shopify's app settings. Disconnecting in MightWork alone is not a Shopify uninstall. Customer privacy requests remain available to the workspace owner even if the plan no longer includes the connector. # Send new MightWork leads to Zapier https://mightwork.us/docs/zapier Use MightWork's New Lead trigger to start a Zap when a contact enters your Leads inbox. The native Zapier integration is in release preparation and is not publicly listed yet. Request access from MightWork before following the native-app steps. ## Requirements - A MightWork workspace owner with Leads Connector access and agent access enabled. - A dedicated API key with leads:read permission. Keep it in your password manager and Zapier's secure connection field. - A Zapier account with access to the MightWork integration. Zapier plan requirements depend on the destination and workflow you choose. ## 1. Create a dedicated key Select your workspace in MightWork. In Connections, enable agent access and select Save access. Then create a key named Zapier with Read leads and contacts (leads:read) permission. Choose an expiry that fits your rotation schedule. Copy the key once to your password manager. It belongs to this workspace; changing the dashboard's selected workspace does not move an existing Zapier connection. Open Connections: https://app.mightwork.us/connections ## 2. Connect the New Lead trigger After MightWork grants integration access, create a Zap and choose MightWork as the trigger app. Select New Lead. Connect an account and enter the API key in Zapier's credential field. Check that the connection identifies the correct MightWork workspace. Never paste the key into a prompt or a normal Zap field. Open your Zaps: https://zapier.com/app/zaps ## 3. Map and test the destination Test the trigger with a lead containing only contact details you control. Map the returned name, email and any other needed fields into your chosen destination. Zapier's test may run the destination action. Review it before testing, particularly if it sends a message or changes a customer record. Keep the lead id in the destination if you need to recognize retries. Open your Leads inbox: https://app.mightwork.us/leads ## 4. Turn on and verify Publish or turn on the Zap. Create one fresh test lead in MightWork, then check Zapier's run history and the destination record. A successful trigger test alone does not prove the live Zap is subscribed. Verify the new lead arrived once and that it contains the expected fields. This integration triggers on new leads; it does not import historical leads or update MightWork records. Open Zap history: https://zapier.com/app/history ## Troubleshooting ### MightWork does not appear in Zapier The integration is not publicly listed yet. Request access from MightWork. A Zapier webhook URL and the native MightWork app are different connection methods; do not paste a webhook URL into the API key field. ### Authentication failed or permission denied Check that the key has not expired or been revoked, the owner still belongs to the workspace, agent access is enabled, and leads:read plus Leads Connector access are allowed. Create a replacement key in the same workspace and reconnect it in Zapier. Turn the Zap off and back on with the replacement connection so it creates a new subscription, then verify a fresh lead arrives. ### The test works but new leads do not arrive Confirm the Zap is on, then create a fresh lead. Check Zap history and MightWork's Leads Connector delivery status for failures. Correct the connection before retrying an action that could send a message or create duplicates. ## Remove Turn off or delete the Zap to unsubscribe its trigger. Revoke its dedicated API key in MightWork to stop that credential's access. Revocation is checked before queued deliveries. Removing a connection does not erase data already received by Zapier or the destination.