
NAUT wrote this guide from n8n's own docs, read on 16 November 2026. n8n does not endorse NAUT. By the end you will have n8n crypto contacts from NAUT in a workflow, 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 n8n's HTTP Request node, with its Authentication set to a Header auth credential that holds your key.
Data note. The counts come from NAUT's own database, read on 16 November 2026, over its 14,680 live contacts (archived and merged rows left out). The setup steps come from 2 n8n doc pages (listed under Sources), and NAUT has not run them inside n8n. 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.
- An n8n workflow you can edit. On n8n's plans, the docs do not name a plan for the HTTP Request node or Header auth.
- 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 n8n crypto contacts with the NAUT API?
This is the whole n8n API key integration, the n8n NAUT API setup in 8 steps, written from n8n's 2 doc pages. Each label below is 1 those pages use.
- Mint your key at https://naut.so/developer and keep it out of any shared note.
- In your workflow, add an HTTP Request node.
- In the node's URL parameter, enter
https://api.naut.so/v1/people?q=founder. n8n's page says: "Enter the endpoint you want to use." - Under Authentication, choose the generic credentials path and pick Header auth. n8n lists the generic types as "Basic auth, Custom auth, Digest auth, Header auth, OAuth1 API, OAuth2 API, Query auth, and Simplified Custom Auth."
- Create the Header auth credential, so the key is stored as an n8n credential. n8n's credentials page gives the pattern: "with the Name set to Authorization and the Value set to Bearer ". Set Name to
Authorizationand Value toBearer $NAUT_KEY, putting your key in place of$NAUT_KEY. - Optionally, move the search out of the URL: turn on Send Query Parameters and add
qwith the valuefounder. n8n's page says: "If the API you're interacting with supports them and the request you're making needs a filter, turn this option on." - Leave Send Headers off for the key. That setting exists for extra headers ("Use this parameter to send headers with your request."), and the credential already sends
Authorization. - Run the node once and read the output: the people sit under
data, with the match count intotal.
Each run is 1 NAUT call at 5 credits, so test once before you put the node on a schedule or a loop.
Which NAUT calls work best in n8n?
These calls fit an n8n crypto contact API node. Prices are NAUT's credits per call.
/v1/people?q=founder: people matching founder; 4,641 founder titles on NAUT. 5 credits./v1/people?q=partnerships: people matching partnerships; part of 505 BD titles. 5 credits./v1/search?q=founder: up to 12 projects and 12 people. 5 credits./v1/people/{id}?include=private: 1 profile's email, phone, Telegram, LinkedIn. 10 credits the first time, then 5./v1/me: your account, withsampleMode. 0 credits.
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 n8n crypto contacts fields?
Each person under data carries these fields. Use them in later nodes, for a filter or a CRM write. The example column is NAUT's record for Adam Reeds, Co-Founder & CEO of Ledn, 1 of the 4,641 live founder titles.
| Field | Example | Use in n8n |
|---|---|---|
name |
Contact name in the next node | |
jobTitle |
Co-Founder & CEO | Filter founders from other titles |
company |
Account or company field | |
twitterHandle |
On file | Social field for outreach |
hasTelegram |
false | Route people you can reach on Telegram |
hasEmail |
false | Route people with an email on file |
hasLinkedin |
false | Route people with a LinkedIn on file |
NAUT's data shows 2,164 of the 4,641 live founder titles have a Telegram handle on file and 252 have an email on file. Of the 505 BD or partnerships titles, 309 have a Telegram on file. The flags say whether a value is on file, never the value. 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. Point a second HTTP Request node at GET https://api.naut.so/v1/me, with the same credential, 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. Start your 7-day trial at https://naut.so and run step 8 again.
- Build on a free keyEvery row 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 and Crypto lead list: 3 API calls, 53 decision makers, 120 credits.
Instructions for AI agents
- Base URL:
https://api.naut.so/v1. Every call is GET and returns JSON. - Header:
Authorization: Bearer $NAUT_KEY, stored in n8n as a Header auth credential on the HTTP Request node. - 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. Re-check the credential's Value is
Bearer, a space, then the 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). Slow the loop down. - 410
HOST_RETIRED: the node uses the old host. Point it athttps://api.naut.so. - An HTML 404: the URL went to naut.so, which has no API routes. Use
api.naut.so.
n8n crypto contacts FAQ
Can I use the NAUT API in n8n?
Yes. n8n's HTTP Request node takes an endpoint URL and a Header auth credential, 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 n8n need a paid plan for this?
n8n's HTTP Request credentials page, read on 16 November 2026, does not name a plan for the HTTP Request node or Header auth. 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 n8n?
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 n8n, and reveals of contact values work after that first payment.
How do I pull crypto contacts into n8n with an API key?
Add n8n's HTTP Request node with GET https://api.naut.so/v1/people?q=founder and a Header auth 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 n8n?
An agent can configure the n8n node 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
- n8n docs, HTTP Request node, read 16 November 2026: https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/
- n8n docs, HTTP Request credentials, read 16 November 2026: https://docs.n8n.io/integrations/builtin/credentials/httprequest/
- 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, 505 with BD or partnerships titles.