ListKit Zapier webhook bridge

Files (1)

• SKILL.md

SKILL.md (first lines)

# ListKit Zapier webhook bridge

ListKit cannot POST with our Authorization Bearer header directly. Bridge:

**ListKit Integrations → Manage webhooks (Lead category updated) → Zapier Catch Hook (Zap step 1) → Zapier Webhooks POST with Bearer (Zap step 2) → this bot's webhook routine.**

## Hard rule (do not skip)
Agents often jump straight to Zapier Bearer POST and forget ListKit. **Both ends are required:**

1. **ListKit** must POST category updates into the **Zapier Catch Hook** URL (Zap step 1).
2. **Zapier** must then POST that JSON to the Grok Bot webhook with `Authorization: Bearer <key>` (Zap step 2).

If ListKit Integrations webhooks are empty or still point elsewhere, the bridge is incomplete even when Zapier looks fine.

## Operator does only this
1. Log into **ListKit** (`next.listkit.io`) on this computer
2. Log into **Zapier** (`zapier.com`) on this computer
3. After you create the reply-catcher webhook routine, paste from that Grok Bot routine panel:
   - **webhook URL**
   - **Bearer / sender key**

Script:
> Log me into ListKit and Zapier. I'll create the reply catcher. Paste the webhook URL and Bearer from that routine in Grok Bot. I'll set up Zapier and the ListKit Integrations webhook myself.

## You do everything else (strict order)

### A. Grok Bot catcher
1. Create the webhook reply-catcher routine
2. Take their pasted URL + Bearer (secrets: use for Zapier only; never store in skills/template memory)

### B. Zapier Zap step 1 (Catch Hook) FIRST
3. In **Zapier**, create a Zap with trigger **Webhooks by Zapier → Catch Hook**
4. Copy the Catch Hook URL Zapier gives you (this is step 1 only; do not add Bearer auth here)

### C. ListKit Integrations → Manage webhooks (MANDATORY)
5. In **ListKit**: open left-nav **Integrations** → **Manage webhooks** → **Add webhook** (docs article 16774358)
6. Paste the **Zapier Catch Hook URL**, set Event Type **Lead category updated**, add signing secret if prompted, Save, then **Send test**
7. Confirm the webhook shows the Catch Hook URL, not the Grok Bot Bearer URL
8. Do **not** put the Grok Bot Bearer webhook URL into ListKit. ListKit has no Bearer header support.
9. Do **not** email the Catch Hook to support@listkit.io for sending-tool config; self-serve Manage webhooks is the documented path.

### D. Zapier Zap step 2 (Bearer POST) AFTER ListKit is wired
10. Add Zapier action **Webhooks by Zapier → POST** (or Custom Request)
11. URL = Grok Bot webhook URL from the routine panel
12. Header `Authorization: Bearer <key>` from the same panel
13. Pass through the Catch Hook JSON body
14. Publish the Zap

### E. Prove both hops
15. Trigger a test category change in ListKit (or Zapier test with a real ListKit payload)
16. Confirm Catch Hook receives it, then this bot's routine wakes
17. Delete duplicate Zaps / webhooks

## Failure modes
- Zapier Bearer step configured but ListKit Manage webhooks blank → **no wakes** (most common miss)
- ListKit webhook set to Grok Bot URL directly → ListKit cannot send Bearer; use Catch Hook only
- Catch Hook URL changed after ListKit save → re-paste into Manage webhooks

## Notes
- Payload usually has no reply body. Always open Master Inbox.
- Prefer in-app ListKit Manage webhooks over Gmail-notification fallbacks.
- Optional related UI: Email Engine → Settings → Positive-reply notifications (on by default; Interested / Meeting Booked; optional forward address). Does not replace the Catch Hook bridge.
- Do not hand them a long Zap click-path; do the wiring yourself once logged in.
- Do not require a Gmail marketplace plugin for this bridge.

From 10xcoldleads/listkit-wizard, MIT.

More from 10xcoldleads/listkit-wizard