Use Twenty CRM with an AI Browser for Lead List Building

If you use Twenty CRM and you regularly need to build a verified lead list, the bottleneck is usually the same: Twenty CRM holds part of the context, but lead list building also needs signals that live outside it - on the public web, in LinkedIn, in news, in other connected apps. Strawberry is built to combine the Twenty CRM context with the rest of the browser, and run the full workflow as a companion you can re-trigger every week.

This page describes specifically how Strawberry handles lead list building when Twenty CRM is one of the inputs. It names the Twenty CRM surfaces involved, the signals the workflow actually needs, an example prompt you can paste, and what a good output looks like.

The job a SDR, marketer, founder doing outbound is trying to do

The goal of lead list building is to produce a clean, enriched, dedup'd list of N contacts who match ICP and have at least one buying signal. The success metric is concrete: bounce rate below 5%, dedup rate above 95%, and at least 30% of leads with a fresh signal. That definition matters because it shapes what Twenty CRM needs to contribute to the workflow.

What signals lead list building actually needs

For each signal below, here is whether Twenty CRM can contribute directly or whether Strawberry has to find it via the browser:

• ICP criteria (industry, size, geo, stack) - Twenty CRM does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Title match including variants (Head of, VP, Director of) - Twenty CRM does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Verified email pattern - Twenty CRM does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Phone number (when reachable from source) - Twenty CRM does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Recent buying signals (hiring, funding, product launch) - Twenty CRM does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Existing CRM membership (to filter out already-contacted) - Twenty CRM stores or surfaces this directly. Strawberry reads it through the connected integration.

What Strawberry can do inside Twenty CRM

Native Strawberry integration with read + write across all core objects; ideal for CRM hygiene, batch enrichment, and pipeline triage.

Twenty CRM surfaces Strawberry uses for this workflow: people, companies, opportunities, notes, tasks.

How Strawberry runs lead list building with Twenty CRM

1. Strawberry opens the Twenty CRM people that contains the relevant context.
2. The companion pulls related context from Twenty CRM (companies, history, attached files) where it exists.
3. For the parts Twenty CRM does not store, Strawberry uses the browser - web search, LinkedIn, news, the prospect's website.
4. Strawberry synthesises the output in the shape this workflow needs: A CSV or sheet with one row per lead.
5. A human reviews before any external action (send, update, post). Then the approved output is saved back to Twenty CRM or your system of record.

Example Strawberry prompt

Paste this in a new Strawberry chat with Twenty CRM connected. Adjust the specifics to your actual ICP, role, or topic.

Read this Twenty CRM people and any linked context.
Then run a full lead list building workflow on it. Use the browser to fill any gaps not in Twenty CRM.
Return the output in the shape we use for lead list building: A CSV or sheet with one row per lead: name, title, company, email, LinkedIn URL, signal, source.
Do not send anything externally. Save the draft to me to review.

What a good lead list building output looks like

Here is what a finished output for lead list building should look like in practice. The specifics will change for your use case, but the shape should look similar:

• Goal: 75 Head of Growth contacts at Series A-B SaaS in DACH
• Sources: a CRM-clean filter, a ZoomInfo/Apollo enriched pull, and a LinkedIn sweep with manual review
• Output: Google Sheet 'DACH-growth-2026-W23' with columns name, title, company, work email, LinkedIn URL, signal (hiring or funding), source notes

Why Twenty CRM for this, and where to use a different tool

Twenty CRM is strong for this workflow because Native Strawberry integration with read + write across all core objects; ideal for CRM hygiene, batch enrichment, and pipeline triage.

Where Twenty CRM falls short Some create endpoints require sequential calls (~800ms apart) to avoid rate limits; certain custom-field updates must go through update_record.

Consider also Google Sheets for one-off lists.

Common mistakes when running lead list building

• Guessing email patterns and getting bounced
• Including duplicates because the source mixes work and personal emails
• Padding the list with leads who don't match ICP just to hit a count target

Connecting Twenty CRM to Strawberry

Twenty CRM is a connected app; uses API key. Once connected, the companion can read the surfaces above without re-authenticating, and any write action still requires explicit human approval the first time the workflow runs.

Caveats

Do not let any AI agent send emails, update CRM records, or change shared systems without a clear approval step. Strawberry is strongest when the workflow combines browser context with connected-app context and a human review for sensitive actions.

When Twenty CRM + Strawberry is NOT the right fit for lead list building

Skip this setup if any of the following is true:

• You don't actually need Twenty CRM signals. If everything you need lives on the public web, drop the Twenty CRM step and let Strawberry run on URLs alone - it's faster.
• A known Twenty CRM constraint blocks the speed gain: Some create endpoints require sequential calls (~800ms apart) to avoid rate limits.
• The buyer (SDR, marketer, founder doing outbound) doesn't own the decision. If the brief gets handed to someone who'll redo the research, the audit-trail-in-Strawberry advantage is wasted.

3 mistakes that kill this workflow

1. Guessing email patterns and getting bounced. Twenty CRM is one input. Strawberry's edge is combining it with everything else. Stop at Twenty CRM-only signals and you'd have been faster with native Twenty CRM reports.
2. Including duplicates because the source mixes work and personal emails. Pre-check Twenty CRM for a recent touch or duplicate before Strawberry acts on the output. A duplicate hit burns the relationship.
3. Padding the list with leads who don't match ICP just to hit a count target. Strawberry is built so a human reviews before any external action. Skipping that review to save time is how you ship a wrong fact to a real person.

Honest tradeoff vs alternatives

You could build a verified lead list inside Twenty CRM alone using its native features, or with a dedicated lead list building tool. Twenty CRM alone gives you tighter data fidelity but misses every signal that lives off-platform. A specialised lead list building tool gives you better dashboards but its scope ends where its integrations end, and most of the real signal still lives on the open web.

Strawberry's edge with Twenty CRM: Native Strawberry integration with read + write across all core objects; ideal for CRM hygiene, batch enrichment, and pipeline triage. The price you pay: an agent run takes 30-90 seconds; a native Twenty CRM action loads in 2. For a one-off question you already know the answer to, use Twenty CRM directly. For an output you'll redo every week or every account, route it through Strawberry as a saved routine so the synthesis happens once and re-runs automatically.

What a real output looks like

• Goal: 75 Head of Growth contacts at Series A-B SaaS in DACH
• Sources: a CRM-clean filter, a ZoomInfo/Apollo enriched pull, and a LinkedIn sweep with manual review
• Output: Google Sheet 'DACH-growth-2026-W23' with columns name, title, company, work email, LinkedIn URL, signal (hiring or funding), source notes