Workspace documentation
Send new MightWork leads to Zapier
Use MightWork's New Lead trigger to start a Zap when a contact enters your Leads inbox.
Before you install
What you need
- 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.
What moves between your apps
- 1New MightWork lead — Not started
- 2Zapier New Lead trigger — Not started
- 3Your chosen destination — Not started
Your checklist: 0 of 4 steps marked done
Use this checklist as you follow the steps. It resets when you leave; it does not check your connection automatically.
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 Connections2. 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 Zaps3. 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 inbox4. 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 historyIf something does not work
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.
Pause, disconnect or 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.