Connect Zapier to GuardenerAI with the API.

Step by step

1. Pick the trigger

   Start the Zap with the app where your leads arrive: a form, an ad platform, a spreadsheet row. Run a test so Zapier has a sample with a first name, last name and email to map.

2. Look the person up by email

   Add Webhooks by Zapier with the GET action. Set the URL to your leads endpoint with an exact email filter, and add a header named X-Api-Key with your key. Lower-case the email first (Formatter by Zapier can do it), because the match is case-sensitive.

   Copy

   https://YOUR-ORG.guardenerai.com/api/leads?filter=email:equals:{{email}}

3. Branch on what came back

   Add Paths. One path continues only when totalElements is 0 (a new lead). The other continues when it is greater than 0 (a lead you already have), and uses content[0].id as the lead’s id. If you only want new leads, a single Filter on totalElements is enough.

4. Create the new lead

   On the new-lead path add Webhooks by Zapier with Custom Request, method POST, to /api/leads. Add the X-Api-Key header and Content-Type: application/json, and map the trigger fields into the body. firstName, lastName and email are required.

   Copy

   {
     "firstName": "{{first_name}}",
     "lastName": "{{last_name}}",
     "email": "{{email}}",
     "phone": "{{phone}}",
     "company": "{{company}}",
     "message": "{{message}}",
     "sourceMedium": "zapier",
     "sourceCampaign": "spring open day"
   }

5. Or update the lead you found

   On the other path, use Custom Request with method PUT to /api/leads/{id}. A PUT replaces the whole record, so map every field you want to keep, including the ones that did not change. Publish the Zap and send a test lead through.