
NAUT wrote this guide from Pipedream's own docs, read on 16 November 2026. Pipedream does not endorse NAUT. By the end you will have Pipedream 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 Pipedream's Node.js code step, making the request with axios.
Data note. The counts come from NAUT's own database, read on 16 November 2026. The setup steps come from Pipedream's page on making HTTP requests with Node.js (listed under Sources), and NAUT has not run them inside Pipedream. 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. Plan ahead: a notice on the same Pipedream docs page reads "Workflows and String are shutting down on March 31, 2027."
What do you need before you start?
- A NAUT account and an API key, minted by a human at https://naut.so/developer.
- A Pipedream workflow you can edit. On Pipedream's plans, the docs do not name a plan: the HTTP requests page states no plan or price for Node.js code steps.
- 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 Pipedream crypto contacts with the NAUT API?
This is the whole Pipedream API key integration, the Pipedream NAUT API setup in 6 steps, written from Pipedream's HTTP requests page.
- Mint your key at https://naut.so/developer and keep it out of any shared note or step code.
- Store the key as a Pipedream environment variable named
NAUT_KEY. Pipedream's page says: "Alternatively, you can use Environment Variables as well for simple API key based GraphQL APIs." The same pattern fits a REST key like NAUT's. - In your workflow, add a Node.js code step and import axios at the top of it.
- In the step, call axios with the method
GETand the URLhttps://api.naut.so/v1/people?q=founder. - Add the key as a header. Pipedream's page says: "You pass HTTP headers in the
headersobject of theaxiosrequest:". SetAuthorizationtoBearer $NAUT_KEY, reading the value in code with Node'sprocess.env.NAUT_KEY, so the key never sits in the step itself. - Run the step once and read the response: 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 workflow on a schedule or a loop.
Which NAUT calls work best in Pipedream?
These calls fit a Pipedream crypto contact API step. 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 502 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 502 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 Pipedream crypto contacts fields?
Each person under data in the axios response carries these fields. Read them in your code step, then filter or send them on to a CRM. For example, NAUT's record for Adam Reeds carries the jobTitle Co-Founder & CEO and hasTelegram false, so a Telegram route would skip him. Anyone listed can ask NAUT to remove their page at https://naut.so/legal/data-deletion.
| Field | Holds | Use in Pipedream |
|---|---|---|
name |
Full name | Contact name |
jobTitle |
Current title | Keep founders only |
company |
Company | Account field |
twitterHandle |
X handle | Social field |
hasTelegram |
true or false | Route Telegram leads |
hasEmail |
true or false | Route email leads |
hasLinkedin |
true or false | Route LinkedIn leads |
NAUT's data shows 2,164 of the 4,641 live founder titles have a Telegram handle 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.
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. Add a second axios call in the step to GET https://api.naut.so/v1/me, with the same header, 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 4 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 Export crypto contacts to CRM: 5,000 rows, 2 paid columns.
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 stored as a Pipedream environment variable and passed in the axiosheadersobject. - 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 the header reads
Bearer, a space, then the key, and that the environment variable name matches your code. - 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 step 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.
Pipedream crypto contacts FAQ
Can I use the NAUT API in Pipedream?
Yes. A Pipedream Node.js code step can send an axios request with headers, 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 Pipedream need a paid plan for this?
Pipedream's HTTP requests page, read on 16 November 2026, does not name a plan for Node.js code steps. On the NAUT side, a free key returns sample data and a trial or paid key returns live data. The same page says Pipedream Workflows shut down on March 31, 2027.
Is there a free trial for the NAUT API in Pipedream?
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 Pipedream, and reveals of contact values work after that first payment.
How do I pull crypto contacts into Pipedream with an API key?
Use a NAUT key in a Pipedream code step with GET https://api.naut.so/v1/people?q=founder, which covers 4,641 live people with founder in their job title, and NAUT's data shows 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 Pipedream?
An agent can write the Pipedream code step 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
- Pipedream docs, Make HTTP requests with Node.js, read 16 November 2026: https://pipedream.com/docs/code/nodejs/http-requests/
- Pipedream docs, same page at its workflows path, read 16 November 2026: https://pipedream.com/docs/workflows/building-workflows/code/nodejs/http-requests/
- NAUT API docs: https://naut.so/docs/api
- NAUT plans and trial terms: https://naut.so/pricing
- NAUT database, read-only, 16 November 2026: 4,641 live people with founder in their job title, 2,164 of them with Telegram on file, 502 with BD or partnerships titles.