Connect Make to GuardenerAI with the API.

Step by step

1. Start the scenario

   Use the trigger module of the app where your leads arrive, or the Webhooks app’s Custom webhook if another system can post to Make. Run it once so the scenario has sample data to map.

2. Look the person up by email

   Add the HTTP app’s Make a request module, method GET. In Headers, add one named X-Api-Key with your key as the value. Make also offers an API key authentication type that keeps the key in a keychain; if you use it, check the request sends the key in that header. Set Parse response to Yes so the results can be mapped. Lower-case the email in the URL, because the match is case-sensitive.

   Copy

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

3. Route on what came back

   Add a Router with two routes. The first route’s filter passes when totalElements equals 0 (a new lead). The second passes when it is greater than 0, and takes the id of the first item in content as the lead’s id.

4. Create the new lead

   On the first route add Make a request, method POST, to /api/leads, with the same API key credential. Choose application/JSON as the body content type and map the fields. firstName, lastName and email are required.

   Copy

   {
     "firstName": "{{1.first_name}}",
     "lastName": "{{1.last_name}}",
     "email": "{{lower(1.email)}}",
     "company": "{{1.company}}",
     "message": "{{1.message}}",
     "sourceMedium": "make",
     "sourceCampaign": "trade show"
   }

5. Or update the lead you found

   On the second route send a PUT to /api/leads/{id}. A PUT replaces the whole record, so map every field you want to keep. Set Return error if HTTP request fails to Yes on each request, so a rejected call stops the run instead of passing silently.