Typeform → Attio: intake that qualifies itself

Typeform is the best intake form tool. The problem is most teams use it in isolation - responses accumulate in Typeform, someone exports a CSV on Friday, pastes it into the CRM on Monday, and half the context gets lost in translation. Hot leads cool off over the weekend. We wire Typeform directly into Attio. Every submission becomes a Person record (or updates an existing one), carries its answers onto the record as structured fields, runs through a qualification score, and routes high-fit responses into Slack within seconds.

Direction

Typeform → Attio (responses, conditional routing)

Stack

Typeform API, Attio API, n8n, Slack

The what

What this integration actually does

Responses land in Attio as they're submitted - mapped to the right object (Person, Company, custom object like Applications or Referrals), scored on fields that actually indicate fit, and optionally enriched with Clearbit/Clay data before they reach the sales team's view. For gated applications (VC programs, member networks, partnership intake) we add a conditional approval layer so only qualifying responses create a record, and the rest go into a "needs review" bucket.

The how

How we build it

1
Design the Attio object model - usually Person + a custom object like Application or Referral or Inquiry.
2
Register a Typeform webhook on response submission.
3
Parse the response in n8n: normalize fields, look up existing Person by email, enrich if needed.
4
Score the response against whatever qualification rubric you use (fund size, team size, use case keywords).
5
Create or update the Attio record with all answers as structured fields.
6
Route: high-score responses ping the right owner in Slack with a one-line summary and a direct link to the Attio record.

Under the hood

What lives inside the pipeline

Conditional record creation - junk responses don't clutter the CRM.
Answer-to-field mapping with type coercion (dropdowns to Attio options, numbers to numeric fields).
Duplicate detection against existing People by email.
Optional enrichment step (Clay, Clearbit, or a custom lookup).
Slack routing keyed to the response category.

Hard-earned lessons

What we learned the hard way

Typeform question IDs change if someone edits the form. Key on question text or use the hidden question reference IDs, not the auto-generated ones.
Long-form responses can exceed Attio text field limits on import. Truncate or chunk.
Hidden fields from URL parameters are gold for attribution - pass UTM and source through the form URL, capture them on the response.
Don't create a record on every partial submission. Wait for the final submit event or you'll get ghost records.

Case study

Horizons - UHNW member network

Problem

Application Typeforms for new members (and spouse/sibling adds) were sitting in Typeform's dashboard. The ops team manually reviewed and pasted approved members into Attio.

Solution

Typeform → Attio with a qualification layer. Applications create a pending Person record tagged for review, auto-approved ones create full Members linked to their inviter.

Outcome

Application-to-member-record cycle dropped from days to seconds. No more "did we respond to that application?" threads.

FAQ

Questions we get

Yes. We set up a pending queue - applications land as a separate object and don't pollute your main People table until approved.

Same pattern works for all of them. Typeform is just the most common.

Yes - via Typeform's hidden fields and a signed URL from Attio. Useful for renewal or update flows where you don't want the Person to retype their info.