
NAUT wrote this guide from Salesforce's own docs, read on 16 November 2026. Salesforce does not endorse NAUT. By the end you will have Salesforce crypto contacts from NAUT in a flow, 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 Create HTTP Callout, an Action element in Flow Builder that calls the API through a Named Credential.
Data note. The counts come from NAUT's own database, read on 16 November 2026, over its 14,680 live contacts. The setup steps come from 1 Salesforce Trailhead project page (listed under Sources), and NAUT has not run them inside Salesforce. 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.
What do you need before you start?
- A NAUT account and an API key from https://naut.so/developer.
- A Salesforce org where you can build flows. The Trailhead page NAUT read does not name a plan or edition.
- 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 Salesforce crypto contacts with the NAUT API?
This is the Salesforce API key integration in 7 steps. The Flow Builder labels below are the ones on Salesforce's Trailhead page.
- Mint a key at https://naut.so/developer and keep it out of the flow itself. NAUT expects it as the header
Authorization: Bearer $NAUT_KEY. - In Salesforce, set up a Named Credential for
https://api.naut.so. Salesforce's docs say a named credential holds the callout endpoint and its authentication settings, so the key belongs there. The Trailhead page does not show that screen, so follow Salesforce's Named Credential docs for the auth fields. - Open a flow in Flow Builder. "Under Start, click" the Add Element icon, then select Action. The Action configuration panel opens.
- "In the configuration panel, click Create HTTP Callout."
- Enter a Name and Description, then pick your NAUT credential under Named Credential. "The corresponding URL appears below Named Credential", which should read
https://api.naut.so. - On the next page, define the request: a GET to the path
/v1/people?q=founder, so the full call ishttps://api.naut.so/v1/people?q=founder. - Save the flow, then debug and run it. Trailhead puts it this way: "You're ready to run the flow and see the results of your declarative excellence."
Which NAUT calls work best in Salesforce?
These calls fit a Salesforce crypto contact API flow. Credits are NAUT's price per call.
/v1/people?q=founder: people matching founder; 4,641 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, withsampleMode. 0 credits.
The 308 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 Salesforce crypto contacts fields?
Each person under data carries the fields below. The example column is NAUT's record for Sunny Lu, CEO and Co-founder of VeChain, 1 of the 4,641 live founder titles. The right column is a suggested home on a Salesforce record; pick the fields your org uses when you assign the callout's output in later flow elements.
| NAUT field | Example | Salesforce home |
|---|---|---|
name |
Contact name | |
jobTitle |
CEO and Co-founder | Contact title |
company |
Account name | |
twitterHandle |
On file | A custom text field |
hasTelegram |
true | A checkbox field |
hasEmail |
false | A checkbox field |
hasLinkedin |
true | A checkbox field |
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 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. Build a second callout on the same Named Credential to GET https://api.naut.so/v1/me 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.
- 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, kept in the Salesforce Named Credential, never in the flow. - 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 Named Credential sends
Bearer, a space, then the key. - 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. Dropinclude=privateuntil day 7. - 429: over 120 requests a minute, or past the trial's daily share (
TRIAL_DAILY_LIMIT, retry aterror.nextAt). Run the flow less often. - 410
HOST_RETIRED: the credential points at the old host. Set it tohttps://api.naut.so. - An HTML 404: the call went to naut.so, which has no API routes. Use
api.naut.so.
Salesforce crypto contacts FAQ
Can I use the NAUT API in Salesforce?
Yes. Salesforce's Flow Builder has a Create HTTP Callout action that calls an outside API through a Named Credential, and the Salesforce NAUT API setup points it at https://api.naut.so/v1/people?q=founder with a Bearer key. NAUT wrote this from Salesforce's docs and has not run it inside Salesforce.
Does Salesforce need a paid plan for this?
The Salesforce Trailhead page NAUT read on 16 November 2026 does not name a plan or edition for Create HTTP Callout, so check your org's edition with Salesforce. 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 Salesforce?
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,680 live contacts in the same Salesforce flow. 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 Salesforce with an API key?
Store a NAUT key from https://naut.so/developer in a Salesforce Named Credential, then add a Create HTTP Callout action in Flow Builder that sends GET /v1/people?q=founder. That call searches the 4,641 live people NAUT lists with founder in their job title, at 5 credits a call.
Can an AI agent set this up in Salesforce?
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 Salesforce. Agents that speak MCP can also reach NAUT at https://api.naut.so/mcp with the same key.
Sources
- Salesforce Trailhead, Build the HTTP Callout Flow project page, read 16 November 2026: https://trailhead.salesforce.com/content/learn/projects/quick-start-create-http-callouts-with-flow-builder/build-the-http-callout-flow
- NAUT API docs: https://naut.so/docs/api