Use Twenty CRM with an AI Browser for Content Planning

If you use Twenty CRM and you regularly need to plan the next content cycle, the bottleneck is usually the same: Twenty CRM holds part of the context, but content planning 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 content planning 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 content marketer, founder writing for the company, brand lead is trying to do

The goal of content planning is to decide what to publish next week and why, with each piece tied to a specific search query or audience. The success metric is concrete: ratio of published-to-planned > 80%, average time-on-page above 2 minutes, organic traffic up week over week. That definition matters because it shapes what Twenty CRM needs to contribute to the workflow.

What signals content planning actually needs

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

• Current search rankings and traffic - Twenty CRM does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Competitor content gaps - Twenty CRM does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Questions the sales team gets repeatedly - Twenty CRM does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Internal subject-matter expertise - Twenty CRM does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Seasonal or event-driven hooks - Twenty CRM does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Internal data the team could publish - Twenty CRM does not contain this directly. Strawberry uses the browser plus public sources to fetch it.

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 content planning 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 content calendar with each row.
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 content planning workflow on it. Use the browser to fill any gaps not in Twenty CRM.
Return the output in the shape we use for content planning: A content calendar with each row: target keyword/audience, format, hook, draft owner, due date.
Do not send anything externally. Save the draft to me to review.

What a good content planning output looks like

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

• Week 24 - Content plan
• Mon: comparison post 'Strawberry vs Manus' - target 'manus AI alternative' - draft by Laurits - publish Tue
• Wed: customer story Iltihouse - target 'AI for outbound sales' - draft by Lotte - publish Thu
• Fri: weekly product release recap - target loyal users + Github watchers - draft by Charles - publish Fri

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 content planning

• Planning content nobody actually searches for
• No internal owner so the calendar slips week after week
• Writing about generic topics where the team has no edge

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 content planning

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 (content marketer, founder writing for the company, brand lead) 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. Planning content nobody actually searches for. 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. No internal owner so the calendar slips week after week. Pre-check Twenty CRM for a recent touch or duplicate before Strawberry acts on the output. A duplicate hit burns the relationship.
3. Writing about generic topics where the team has no edge. 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 plan the next content cycle inside Twenty CRM alone using its native features, or with a dedicated content planning tool. Twenty CRM alone gives you tighter data fidelity but misses every signal that lives off-platform. A specialised content planning 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

• Week 24 - Content plan
• Mon: comparison post 'Strawberry vs Manus' - target 'manus AI alternative' - draft by Laurits - publish Tue
• Wed: customer story Iltihouse - target 'AI for outbound sales' - draft by Lotte - publish Thu
• Fri: weekly product release recap - target loyal users + Github watchers - draft by Charles - publish Fri