
NAUT wrote this guide from Attio's own docs, read on 16 November 2026. Attio does not endorse NAUT. By the end you will have Attio crypto contacts from NAUT inside 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 the Send HTTP request block in Attio workflows.
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 steps come from 2 Attio pages: the workflows block library and the 20 June 2024 changelog. NAUT checked 12 claims against them, and 10 were confirmed with a quote found on the page. NAUT has not run this setup inside Attio. 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 Attio workspace where you can build workflows. NAUT did not confirm a plan requirement for the Send HTTP request block from the 2 Attio pages it read, so check your own workspace before you build.
- 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 Attio crypto contacts with the NAUT API?
This is the whole Attio API key integration, the Attio NAUT API setup in 8 steps, written from Attio's block library.
- Mint your key at https://naut.so/developer and keep it out of any shared doc.
- In an Attio workflow, add the Send HTTP request block from the utility steps of the block library. Attio's page says: "Send HTTP request sends an HTTP request to another system from a workflow."
- Set the method to GET. Attio's page says: "Supported methods are DELETE, GET, HEAD, PATCH, POST, and PUT." Every NAUT call is a GET request.
- Point the request at
https://api.naut.so/v1/people?q=founder. Add&limit=100for the most rows 1 page holds. - Add the key as a header. Attio's page says: "Add any headers required by the receiving system as header and value pairs." Use the name
Authorizationand the valueBearer $NAUT_KEY, with your key in place of$NAUT_KEY. Attio's 20 June 2024 changelog reads: "Added support for custom headers in the Send HTTP request block," for cases that need a specific authorization header. - Leave the body empty. Attio's page says a body format "is required for requests that include a message body, such as POST and PUT requests." A NAUT call keeps its search terms in the URL, so it sends no body.
- Pass the response body to a Parse JSON block. Attio's page says: "Parse JSON parses a JSON string into structured values you can use in later workflow steps." Its schema sets the shape to extract, so describe the person fields under
data. - Check the first run before you build on it. The block's success output "Returns true when the response status code is in the 200-299 range." A free key's rows carry
"sample": true, andtotalgives the match count.
Header values take "hard-coded text, variables, or a combination of both", and the page NAUT read states no storage or masking method for them. The key sits in the block's Headers fields, so limit who can edit the workflow. Each run is 1 NAUT call at 5 credits, and Attio's page says: "The timeout duration for the Send HTTP request block is 2 minutes."
Which NAUT calls work best in Attio?
These calls fit an Attio crypto contact API block. Credits are NAUT's price per call.
/v1/people+q=founder(5 credits): people matching founder, from 4,641 live founder titles./v1/people+q=partnerships(5 credits): people matching partnerships, part of 308 BD titles./v1/search+q=founder(5 credits): up to 12 projects and 12 people./v1/people/{id}+include=private(10 credits, then 5): 1 profile's email, phone, Telegram, LinkedIn./v1/me(0 credits): your account, withsampleMode.
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, up to 100 with limit; use &page=2 for the next page.
Which founder titles does the call match?
NAUT's data shows these 8 job titles are the most common among the 4,641 live founder matches. Together they hold 3,608 people.
| Job title on NAUT | Live people |
|---|---|
| Co-Founder | 1,665 |
| Founder | 813 |
| Co-Founder & CEO | 629 |
| Co-Founder & CTO | 197 |
| Co-Founder & COO | 97 |
| Founder & CEO | 95 |
| Co-founder | 84 |
| Founder and CEO | 28 |
A BD lead who sells to technical buyers can add a filter step on jobTitle after Parse JSON and keep the 197 Co-Founder & CTO rows.
How do I map Attio crypto contacts fields?
Each person under data carries these fields. Define each one in the Parse JSON schema, and it becomes a value later workflow steps can use. Each example 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.
name: Yi He. The person's name.jobTitle: Co-CEO and Co-Founder. A title attribute, or a filter.company: Binance. The company the person works at.twitterHandle: On file. A social attribute 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 Send HTTP request block 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 workflow changes between the 2 modes except the key in the Headers fields. 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, set as a header and value pair in Attio's Send HTTP request block. - 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 header value is
Bearerplus the key. Attio's page also notes: "Attio may also block other headers as needed to maintain platform security." - 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). Run the workflow less often. - 410
HOST_RETIRED: the URL 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.
Attio crypto contacts FAQ
Can I use the NAUT API in Attio?
Yes. Attio's Send HTTP request workflow block supports GET and takes header and value pairs, so it can carry 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 Attio need a paid plan for this?
NAUT did not confirm an Attio plan requirement for the Send HTTP request block from the 2 Attio pages it read on 16 November 2026, so check your workspace. 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 Attio?
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 Attio, and reveals of contact values work after that first payment.
How do I pull crypto contacts into Attio with an API key?
Add a Send HTTP request block with GET https://api.naut.so/v1/people?q=founder and an Authorization: Bearer header, then a Parse JSON block for the fields. 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 Attio?
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
- Attio Help Center, Workflows block library (no last-updated date shown), read 16 November 2026: https://attio.com/help/reference/automations/workflows/workflows-block-library
- Attio changelog, 20 June 2024, read 16 November 2026: https://attio.com/changelog/2024/changelog-june-20-2024
- 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, 2,164 of those with Telegram on file, 308 with BD or partnership titles.