All articles

HubSpot crypto contacts: how to connect the NAUT API

4,663 HubSpot + NAUT API live people on NAUT with founder in their job title, 1 webhook away in HubSpot

NAUT wrote this guide from HubSpot's own docs, read on 17 November 2026. HubSpot does not endorse NAUT. By the end you will have HubSpot crypto contacts from NAUT in a workflow, pulled with 1 call, GET https://api.naut.so/v1/people?q=founder, where NAUT tracks 4,663 live people with founder in their job title as of 17 November 2026. The feature that does it is Send a webhook, a workflow action that sends the call with your NAUT key in the request header.

Data note. The counts come from NAUT's own database, read on 17 November 2026, over its 14,763 live people. The setup steps come from 1 HubSpot Knowledge Base page (listed under Sources), and NAUT has not run them inside HubSpot. The q parameter matches names and handles as well as job titles, so the total a live call returns can sit above the 4,663 title matches.

What do you need before you start?

  • A NAUT account and an API key from https://naut.so/developer.
  • A HubSpot account with Data Hub Professional or Enterprise, the subscriptions the Send a webhook page lists for this action.
  • HubSpot user rights: the page says setting up webhook actions needs Edit permissions for workflows or Super Admin, and publishing needs Publish permissions for workflows.
  • 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 HubSpot crypto contacts with the NAUT API?

This is the HubSpot API key integration in 8 steps. The labels in quotes are copied from HubSpot's page.

  1. Mint a key at https://naut.so/developer. NAUT expects it as the header Authorization: Bearer $NAUT_KEY.
  2. Store the key as a HubSpot secret. HubSpot's page says "The secret value must be in the format Bearer [YOUR_TOKEN].", so the value is Bearer $NAUT_KEY with your real key in place of $NAUT_KEY.
  3. In HubSpot, click More, then go to Automation > Workflows. Open a workflow or create a new one.
  4. In the workflow editor, "click the + plus icon to add an action."
  5. "In the left panel, in the Data ops section, select Send a webhook."
  6. "Click the Method dropdown menu and select GET." Every NAUT call is a GET.
  7. Enter the webhook URL https://api.naut.so/v1/people?q=founder. HubSpot notes: "Webhook URLs are restricted to a secure protocol and must begin with HTTPS." The page adds that GET query parameters can come from HubSpot properties or static values, so q can also be a fixed word.
  8. Set the authentication type to API key, with Authorization as the API key name. "Click the API key location dropdown menu. Then, select either Query parameters or Request header." Pick Request header, then choose your NAUT secret from the API key dropdown.

When you test the action, expect this: "For security reasons, the API key will not display in any test requests."

Which NAUT calls work best in HubSpot?

These calls fit a HubSpot crypto contact API webhook. Every path below sits under /v1, and credits are NAUT's price per call.

Call What it returns Credits
/people?q=founder 4,663 founder titles 5
/people?q=partnership Part of 309 BD titles 5
/search?q=founder Up to 12 projects, 12 people 5
/people/{id} 1 profile's channels, with include=private 10, then 5
/me Your account, sampleMode 0

The 309 counts live titles with business development, partnership or BD in them, so 1 q=partnership 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 HubSpot crypto contacts fields?

Each person under data in the response carries the fields below. The HubSpot page NAUT read covers sending the request, not storing the reply, so the right column is a suggested home on a HubSpot contact record. Check HubSpot's docs for using webhook output in later workflow actions.

For example, NAUT's record for Kevin He, Co-Founder of Bitlayer, carries hasTelegram true, hasEmail false and hasLinkedin true, so a Telegram route would keep him. Anyone listed can ask NAUT to remove their page at https://naut.so/legal/data-deletion.

Field Holds HubSpot home
name Full name Contact name
jobTitle Current title Job title
company Company Company name
twitterHandle X handle Custom text property
hasTelegram true or false Custom checkbox
hasEmail true or false Custom checkbox
hasLinkedin true or false Custom checkbox

NAUT's data shows 2,164 of the 4,663 live founder titles have a Telegram handle on file, and 171 of the 309 BD titles do. 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 Send a webhook action to GET https://api.naut.so/v1/me with the same secret and check 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.

From sample rows to live founders in HubSpot
  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,663 founder titles, flags included.
  3. Reveal after day 7include=private works once the first payment clears.

Related reading on NAUT: Salesforce crypto contacts: how to connect the NAUT API and Attio crypto contacts: how to connect the NAUT API.

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, kept in a HubSpot secret picked from the API key dropdown, never typed into the URL.
  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. Check the secret reads Bearer, a space, then the key, and that the API key location is Request header.
  • 402: a paid key is out of credits, and nothing was charged. Check your plan 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). Enroll fewer records at once.
  • 410 HOST_RETIRED: the webhook URL points at the old host. Set it to https://api.naut.so.
  • An HTML 404: the call went to naut.so, which has no API routes. Use api.naut.so.

HubSpot crypto contacts FAQ

Can I use the NAUT API in HubSpot?

Yes. HubSpot's Send a webhook workflow action can send a GET with an API key in the request header, and the HubSpot NAUT API setup points it at https://api.naut.so/v1/people?q=founder with a Bearer key stored as a secret. NAUT wrote this from HubSpot's docs and has not run it inside HubSpot.

Does HubSpot need a paid plan for this?

Yes. The HubSpot page NAUT read on 17 November 2026 lists Send a webhook under Data Hub Professional and Enterprise. 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 HubSpot?

Yes. NAUT's 7-day trial runs on Essential or Pro monthly, first charged on day 7, and a trial key returns live data from NAUT's 14,763 live people in the same HubSpot workflow. Verified Telegram, email and LinkedIn values unlock after that first payment; start a 7-day trial at https://naut.so.

How do I pull crypto contacts into HubSpot with an API key?

Store a NAUT key from https://naut.so/developer as a HubSpot secret, then add a Send a webhook action to a workflow that sends GET /v1/people?q=founder with the key in the Request header. That call searches the 4,663 live people NAUT lists with founder in their job title, at 5 credits a call.

Can an AI agent set this up in HubSpot?

An agent can build the NAUT call and read the results once a human has minted the key at https://naut.so/developer and stored it in HubSpot. Agents that speak MCP can also reach NAUT at https://api.naut.so/mcp with the same key.

Sources

Browse all articles