
NAUT wrote this guide from Make.com's own docs, read on 16 November 2026. Make.com does not endorse NAUT. By the end you will have Make.com crypto contacts from NAUT in your scenario, pulled with 1 call, GET https://api.naut.so/v1/people?q=founder, where NAUT tracks 4,641 live people with founder in their job title as of 16 November 2026. The feature that does it is the HTTP app's Make a request module, which sends a request to any URL that begins with https://.
Data note. The counts come from NAUT's own database, read on 16 November 2026, over its 14,680 live contacts (archived rows left out). The setup steps come from 1 page, Make.com's HTTP app docs, and NAUT has not run them inside Make.com. The q parameter matches names and handles as well as job titles, so the total a live call returns can sit above the 4,641 title matches: read total from the response.
What do you need before you start?
- A NAUT account and an API key, minted by a human at https://naut.so/developer.
- A Make.com scenario. On Make.com's plans, the docs do not name a plan for the HTTP app.
- Start a 7-day trial at https://naut.so to get live data (on Essential or Pro monthly, first charged on day 7). A free account's key returns sample data, so you can build the setup first.
How do I pull Make.com crypto contacts with the NAUT API?
This is the whole Make.com API key integration, the Make.com NAUT API setup in 7 steps, written from the HTTP app page. Each step names the field that page uses.
- Mint your key at https://naut.so/developer and keep it out of any shared note or scenario name.
- In your scenario, add the HTTP app and pick its Make a request module.
- In the URL field, enter
https://api.naut.so/v1/people?q=founder. Make.com's page asks you to "Enter the URL of an API endpoint (including the base URL), webhook, or webpage, beginning with https://." - Set the method to GET. The page lists GET, HEAD, POST, PUT, PATCH, DELETE and OPTIONS; every NAUT call is GET.
- Set the authentication type to API key and save your key as a credential. Make.com's page says to "define the authentication details in the dedicated Credentials field". That page does not say which header name the key credential sends, so check that your NAUT calls send
Authorization: Bearerfollowed by your key. NAUT has not run this in Make.com. - Leave the Headers field empty for the key. The page says: "You don't need to use this field to define the authentication credentials and content type".
- Set Parse response to Yes. The page says this is "to structure the output data so that it's easy to map", so later modules can map the people under
dataand the match count intotal.
Each run of the module is 1 NAUT call at 5 credits, so try it on 1 run before you schedule the scenario.
Which NAUT calls work best in Make.com?
These calls fit a Make.com crypto contact API module. Credits are NAUT's price per call.
/v1/people?q=founder(5 credits): people matching founder; 4,641 live founder titles./v1/people?q=partnerships(5 credits): people matching partnerships; part of 505 BD titles./v1/search?q=founder(5 credits): up to 12 projects and 12 people./v1/people/{id}?include=private(10, then 5 credits): 1 profile's email, phone, Telegram, LinkedIn./v1/me(0 credits): your account, withsampleMode.
The 505 counts titles with business development, partnerships or BD in them, so 1 q=partnerships call returns only part of it. Lists return 30 rows by default; add &limit=100 for the most a page holds, and &page=2 for the next page.
How do I map Make.com crypto contacts fields?
With Parse response on, each person under data can be mapped into the next module, such as a sheet, a CRM or a message. The example column is NAUT's record for Yi He, Co-CEO and Co-Founder of Binance, 1 of the 4,641 live founder titles; flags show whether a value is on file, never the value.
| NAUT field | Example: Yi He | Map it to |
|---|---|---|
name |
Contact name | |
jobTitle |
Co-CEO and Co-Founder | Title, or a filter for founders |
company |
Account or company | |
twitterHandle |
On file | Social or outreach field |
hasTelegram |
true | Who you can reach on Telegram |
hasEmail |
false | Who has an email on file |
hasLinkedin |
true | Who has a LinkedIn on file |
NAUT's data shows 2,164 of the 4,641 live founder titles have a Telegram handle on file. The private values (email, phone, Telegram, LinkedIn) stay null until you reveal them with include=private. Reveals return 403 UNPAID_PLAN during the trial and work after the first payment on day 7. Anyone listed can ask NAUT to remove their page at https://naut.so/legal/data-deletion.
How do I test it free with the 7-day trial?
A free account's key returns sample data: synthetic rows in the same shape, marked "sample": true, at 0 credits. Run GET https://api.naut.so/v1/me in a second Make a request module to see sampleMode before you trust a row.
A trial key on the same setup returns live names, titles, companies and the hasTelegram, hasEmail and hasLinkedin flags, though not the contact values. Nothing in the scenario changes between the 2 modes. Start your 7-day trial at https://naut.so and run step 4 again.
- Build on a free keyEvery item comes back marked "sample": true, at 0 credits.
- Start the trialA trial key returns live rows from the 4,641 founder titles, flags included.
- Reveal after day 7include=private works once the first payment clears.
Related reading on NAUT: Clay crypto contacts: how to connect the NAUT API.
Instructions for AI agents
- Base URL:
https://api.naut.so/v1. Every call is GET and returns JSON. - Header:
Authorization: Bearer $NAUT_KEY, with the key saved in the module's Credentials field. Make.com's page does not say which header that credential sends, so confirm the call sends this header. NAUT has not run this in Make.com. - Call for this job:
GET https://api.naut.so/v1/people?q=founder, 5 credits, withpageandlimit(max 100) to walk the list. - Detect sample mode:
"sample": truein the body, aNAUT-Sample: trueheader, orsampleModeonGET /v1/me(free). - A human mints the key at https://naut.so/developer and starts the trial at https://naut.so. There is no programmatic signup.
- Agents that speak MCP can use https://api.naut.so/mcp with the same Bearer key and prices.
What if it does not work?
- 401: the key is missing or wrong. Check that the call sends
Authorization: Bearerfollowed by your key. - 402: a paid key is out of credits, and nothing was charged. Check your plan and credits at https://naut.so/pricing.
- 403
UNPAID_PLAN: a reveal ran during the trial. Dropinclude=privateuntil day 7. - 429: over 120 requests a minute, or past the trial's daily share (
TRIAL_DAILY_LIMIT, retry aterror.nextAt). Space out your scenario runs. - 410
HOST_RETIRED: the module uses the old host. Point the URL athttps://api.naut.so. - An HTML 404: the URL went to naut.so, which has no API routes. Use
api.naut.so.
Make.com crypto contacts FAQ
Can I use the NAUT API in Make.com?
Yes. The HTTP app's Make a request module sends GET requests with saved credentials, which is all a NAUT call needs. GET https://api.naut.so/v1/people?q=founder searches the 4,641 live founder titles NAUT tracks as of 16 November 2026.
Does Make.com need a paid plan for this?
Make.com's HTTP app page, read on 16 November 2026, does not name a plan for the HTTP app. On the NAUT side, a free key returns sample data and a trial or paid key returns live data.
Is there a free trial for the NAUT API in Make.com?
Yes. Start a 7-day trial at https://naut.so on Essential or Pro monthly, first charged on day 7; the trial key returns live names, titles and channel flags in Make.com, and reveals of contact values work after that first payment.
How do I pull crypto contacts into Make.com, and where do I find founders?
Add the HTTP app's Make a request module with GET https://api.naut.so/v1/people?q=founder and your key saved as a credential, and page through the results with page and limit. NAUT's data shows 4,641 live people with founder in their job title, 2,164 of them with a Telegram handle on file. Verified Telegram, email and LinkedIn values unlock after the first payment of a paid NAUT plan; start a 7-day trial at https://naut.so to build on live rows first.
Can an AI agent set this up in Make.com?
An agent can configure the Make.com module from the steps above and NAUT's agent guide at https://naut.so/docs/api/for-ai-agents, or call NAUT directly through the MCP server at https://api.naut.so/mcp. A human still mints the NAUT key and starts the trial.
Sources
- Make.com, HTTP app docs, read 16 November 2026: https://apps.make.com/http (the old help URL www.make.com/en/help/app/http redirects there)
- NAUT API docs: https://naut.so/docs/api
- NAUT plans and trial terms: https://naut.so/pricing
- NAUT database, read-only, 16 November 2026: 14,680 live contacts, 4,641 with founder in their job title, 2,164 of those with a Telegram handle on file, 505 with BD or partnerships titles.