All articles

Zapier crypto contacts: how to connect the NAUT API

4,641 Zapier + NAUT API live people on NAUT with founder in their job title, 1 Zapier action away

NAUT wrote this guide from Zapier's own docs, read on 16 November 2026. Zapier does not endorse NAUT. By the end you will have Zapier crypto contacts from NAUT flowing into a Zap, 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 Webhooks by Zapier, with GET as the event.

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 Zapier help page on sending webhooks in Zap workflows, and NAUT has not run them inside Zapier. 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 Zapier plan with webhooks. Zapier's page says: "Webhooks in Zap workflows are available on Professional, Team, and Enterprise." The Free plan is not on that list.
  • 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 Zapier crypto contacts with the NAUT API?

This is the whole Zapier API key integration, the Zapier NAUT API setup in 7 steps, written from Zapier's webhooks help page.

  1. Mint your key at https://naut.so/developer and keep it out of any shared doc.
  2. In the Zap editor, add an action with the plus icon. Zapier's page says: "Search for and select Webhooks by Zapier."
  3. Open the Event dropdown, pick GET, then click Continue. Zapier's page says: "Use GET if you want the step to retrieve information from a server." Every NAUT call is a GET request.
  4. Fill in the URL field. Zapier's page says: "Enter the destination address in the URL field." Enter https://api.naut.so/v1/people?q=founder. Zapier's page suggests putting URL parameters in the Data fields instead, but q is a documented NAUT query parameter, so keep it in the URL.
  5. Decide on the Data field. The NAUT call needs no body because its search terms sit in the URL, and Zapier's page notes: "If Data is left blank, all fields from the previous step are sent."
  6. Add the key as a header. Zapier's page says: "Add any custom headers in the Headers section, or set up basic authentication in the Basic Auth field." Use the Headers section: name Authorization, value Bearer $NAUT_KEY, with your key in place of $NAUT_KEY. NAUT reads a Bearer header, so leave Basic Auth empty. The page describes no separate secrets store, so the key lives in this action's Headers fields.
  7. Check the first response before you build on it. A free key's rows carry "sample": true, and total gives the match count.

Each run of the action is 1 NAUT call at 5 credits, so test it once before a trigger fires it on every new row.

Which NAUT calls work best in Zapier?

These calls fit a Zapier crypto contact API action. Credits are NAUT's price per call.

  • /v1/people?q=founder: people matching founder, 4,641 live founder titles. 5 credits.
  • /v1/people?q=partnerships: people matching partnerships, part of 308 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, with sampleMode. 0 credits.

The 308 counts live titles with business development, partnership 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 Zapier crypto contacts fields?

Each person under data in the response carries these fields. Zapier's webhooks page does not explain how response fields map into later steps, so this table names what each field is for in the action that receives it, such as a CRM or a sheet. 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.

Field Example Use it for
name Contact name
jobTitle Co-CEO and Co-Founder Filter founders from other titles
company Account or company
twitterHandle On file Social field for outreach
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. Point a second GET action at https://api.naut.so/v1/me 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 Zap changes between the 2 modes except the key in the Headers section. Start your 7-day trial at https://naut.so and run step 4 again.

From sample rows to live founders in Zapier
  1. Build on a free keyEvery row comes back marked "sample": true, at 0 credits.
  2. Start the trialA trial key returns live rows from the 4,641 founder titles, flags included.
  3. 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

  1. Base URL: https://api.naut.so/v1. Every call is GET and returns JSON.
  2. Header: Authorization: Bearer $NAUT_KEY, set in the Headers section of the Webhooks by Zapier action.
  3. Call for this job: GET https://api.naut.so/v1/people?q=founder, 5 credits, with page and limit (max 100) to walk the list.
  4. Detect sample mode: "sample": true in the body, a NAUT-Sample: true header, or sampleMode on GET /v1/me (free).
  5. A human mints the key at https://naut.so/developer and starts the trial at https://naut.so. There is no programmatic signup.
  6. 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 Headers value is Bearer plus 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. Drop include=private until day 7.
  • 429: over 120 requests a minute, or past the trial's daily share (TRIAL_DAILY_LIMIT, retry at error.nextAt). Slow the trigger down.
  • 410 HOST_RETIRED: the URL uses the old host. Point it at https://api.naut.so.
  • An HTML 404: the URL went to naut.so, which has no API routes. Use api.naut.so.

Zapier crypto contacts FAQ

Can I use the NAUT API in Zapier?

Yes. Webhooks by Zapier with the GET event retrieves information from a server, and its Headers section takes the Bearer header 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 Zapier need a paid plan for this?

Yes. Zapier's help page, read on 16 November 2026, says webhooks in Zap workflows are available on Professional, Team and Enterprise, so the Free plan cannot run this NAUT setup. 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 Zapier?

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 Zapier, and reveals of contact values work after that first payment.

How do I pull crypto contacts into Zapier, and where do I find founders?

Add a Webhooks by Zapier action with GET https://api.naut.so/v1/people?q=founder and an Authorization: Bearer header, 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 Zapier?

An agent can follow 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

Browse all articles