Zapier

Zapier lets thousands of apps send Local Wrangler a lead. You connect the Zapier card once, then build a Zap whose last step posts each new contact to the address the card gives you. This page is written to be followed top to bottom.

Connect the card

1. 1
   Open Settings, Integrations, find Zapier under Automation and click Connect, then Connect again in the window that opens.
2. 2
   The confirmation shows your Webhook URL and your Signing Secret. Copy the secret now; it is not shown again. The URL stays on the card.

Build the Zap

1. 1
   In Zapier, create a Zap. For the trigger, pick the app your contacts come from and the event that means a new one, for example a new form entry or a new contact.
2. 2
   Add an action step. Choose the app Webhooks by Zapier and the event POST.
3. 3
   URL: paste the Webhook URL from the card exactly as shown. Its address already identifies your connection, so there is nothing to add to it.
4. 4
   Payload Type: json. A form-encoded body works too; the address accepts application/json, application/x-www-form-urlencoded or multipart/form-data.
5. 5
   Data: add one row for each of name, email, phone and message, and map each to the trigger's matching field. If your source has a separate first and last name, map them to first_name and last_name and they are joined into one name. Any other row you add is kept with the lead under Details, labelled by its name, up to 15 other fields.
6. 6
   Wrap Request In Array: No. Local Wrangler reads one submission per request, and a list is not read.
7. 7
   Headers: add a header named X-Portal-Secret with your Signing Secret as its value. Without it every delivery is refused before anything else is looked at.
8. 8
   Test the action in Zapier, then open Events on the Zapier card. The test appears there as ok with a lead, or with the reason it was refused.

What arrives

Each accepted delivery becomes a form lead tagged zapier, with the name, email, phone and message you mapped and the other fields under Details. It runs through the same checks as every lead: a duplicate of a contact who submitted in the last day is folded onto the open lead, your junk filters apply, and the new-lead alerts go out. A submission that carries a password or a payment field is refused and recorded without its contents, because this address is for lead forms only.

The card reads Awaiting first event until the first delivery arrives, Active from then on, and Quiet when nothing has arrived for more than 7 days.

Refusals, and why some store nothing

A delivery without the header, or with a wrong secret, is refused before its body is read, and appears under Events with the reason but without the payload. That is deliberate: the address travels through other systems' logs, so a delivery that cannot prove it is yours must never write its contents into your panel. Refusals that happen after the secret checked out, such as a missing contact or an unsupported body, keep the payload so you can see what was sent.

Rotate the secret, or disconnect

Rotate secret gives you a new secret at once; the old one stops working, and the URL does not change, so you update one value in the Zap. Reconnect after a disconnect gives you a new URL as well as a new secret. Future deliveries from Zapier will be rejected until you reconnect, and the event history on this card will be cleared.