Argorant in Make.
Make's HTTP → Make a request module drives Argorant directly: structured JSON in, mappable fields out. A native Make app is in preparation; everything below keeps working unchanged.
Create a free account, then mint a key at app.argorant.com/profile → API keys. Name it make so it can be revoked independently. It's shown once — copy it then.
Module: HTTP → Make a request Headers: Authorization: Bearer <your API key> Parse response: Yes (so fields are mappable)
Method: GET
URL: https://argorant.com/api/mcp/people/count
Query: q = logistics ops leaders
country = Netherlands
→ { "count": 8312, ... }# Free, redacted preview GET https://argorant.com/api/mcp/people/preview?q=...&limit=10 # Full details — uses credits GET https://argorant.com/api/mcp/people/reveal?q=...&limit=25
Add an Iterator on the results array, then route each contact to HubSpot, Salesforce, Airtable, Google Sheets, or any Make app.
# Module 1 — create the job
POST https://argorant.com/api/mcp/exports/create
Body (JSON): { "filters": { "q": "fintech CFOs",
"country": "Germany" },
"limit": 500 }
→ { "type": "job", "job_id": "…", "status": "running" }
# Module 2 — Tools → Sleep (60–120 s)
# Module 3 — check status
GET https://argorant.com/api/mcp/exports/{{job_id}}
→ { "status": "completed", "verified_rows": 463,
"downloadable": true }
# Optional: Repeater + Filter (status = completed) for longer jobs
# Module 4 — download the CSV
GET https://argorant.com/api/mcp/exports/{{job_id}}/downloadRows are re-verified at export time and include a verification status column — branch on it with a Router if you only want deliverable emails downstream.
All endpoints share the same query params: q, title, seniority, departments, industry, country, state, city, company_name, company_domain, has_email, has_phone, has_linkedin, verify_status, limit. Full details in the API reference.
Free account, 100 credits included. Counts and searches are always free.