Make: HTTP modules against the Argorant API

Make's HTTP module speaks the Argorant REST API directly, so there is nothing to install and nothing to approve.

Mint an API key under Profile, API keys.
Add an HTTP, Make a request module.
Set the URL to the endpoint you need and add one header: Authorization: Bearer <your key>.
Parse the response as JSON so downstream modules see typed fields.
Add an Iterator over the results and route each contact wherever it belongs.

The four recipes

Count: GET /api/mcp/people/count with your filters as query parameters. Free.
Search: GET /api/mcp/people/preview for redacted rows. Free.
Reveal: GET /api/mcp/people/reveal with a row limit. Spends credits.
Export: POST /api/mcp/exports/create, then poll the status path and download. Spends credits.

The Make HTTP module and Iterator setup for Argorant

Scenario design notes

Put the export polling in its own route with a Sleep module rather than a tight repeater. Set the row limit as a scenario variable so it is visible at a glance, not buried in a request body. Counts are free, so a Make scenario can validate a segment size before it commits to an export in the same run.

Errors map cleanly onto Make's error handling: 402 means the account needs credits and carries a link, 429 means back off, 401 means the key is wrong.