GuidesConnect and integrate

Review the Twenty CRM pipeline

Connect a Twenty Cloud workspace and prepare a weekly review of stalled opportunities, data gaps, and stage changes.

The Twenty CRM pipeline review template reads open opportunities with their stages, amounts, owners, and recent activity, plus the people and companies behind them, and flags opportunities with no recent activity, missing owners or amounts, and stage changes that need a human check, with the record cited for every finding. It follows the revops marketing skill: measure movement, flag operational gaps, and assign the next human action without editing the CRM.

Enable and connect Twenty CRM

An operator must enable MANAGED_MCP_TWENTY_ENABLED. Twenty's authorization server at api.twenty.com supports dynamic client registration, so no static client is needed; connect the Twenty CRM card and authorize with your Twenty Cloud login. Work on Repeat requests api and profile. The managed card covers Twenty Cloud only; self-hosted Twenty instances are not covered.

Set the variable

KeyExampleWhy it is a variable
stalenessDays10What counts as stalled depends on your sales cycle.

Reference it in the instructions as {{stalenessDays}}.

Current beta boundary

Twenty CRM is connection-only until exact authenticated tool schemas are captured and reviewed, so the packaged routine ships as a preview. Because the api scope is not split by read and write, the read-only boundary comes from Work on Repeat's tool policy rather than from the grant: after review, the first manifest should stay with opportunity, person, company, and note reads, and record creation, updates, and deletions must remain blocked or approval-gated.

Recovery

If authorization expires or is revoked, the connection moves to reauthorization_required; reconnect the same card to update it in place.

On this page

Edit this page on GitHub