Integration guide

LeadMerlin + Make

Use Make’s HTTP “Make a request” module. A scenario starts a search, waits for enrichment with a polling loop, then iterates the results into any app Make supports.

Before you start

• A Make account.
• A LeadMerlin API key.

Setup

1. 1

   HTTP — start the search

   Method POST, add header x-api-key, body type Raw / JSON, and enable "Parse response".

   POST https://api.leadmerlin.com/api/v2/searches
   Header: x-api-key: lm_your_key
   {"keyword":"plumber","location_codes":[1026201]}

2. 2

   Poll until completed

   Use a Repeater followed by Sleep and an HTTP GET on the job, with a filter that only continues when status = completed. Keep the repeat count bounded.

   GET https://api.leadmerlin.com/api/v2/jobs/{{job_id}}

3. 3

   Get results

   HTTP GET the results with limit=200. If has_more is true, repeat with cursor = next_cursor.

   GET https://api.leadmerlin.com/api/v2/jobs/{{job_id}}/results?limit=200&cursor={{next_cursor}}

4. 4

   Iterate and send

   Add an Iterator on businesses[], then map name, owner, email, phone and phone_type into Google Sheets, Airtable or your CRM module.

Location codes in these examples are placeholders — always look yours up with GET /v2/locations first.

Tips

• Store the key in a Make connection or data store rather than typing it into every module.
• Each module run counts toward your Make operations; poll every 20–30 seconds rather than every few seconds.

API at a glance

All calls use the x-api-key header except the demo endpoints. Base URL: https://api.leadmerlin.com/api

Related