Companies, People, Opportunities
- Direction
- Twenty → Kaiju
- Cadence
- Initial reconciliation + record changes
- Purpose
- Account universe, CRM identity, ownership, relationships, opportunity state, and stakeholder context.
Twenty integration
See the account from both sides of the CRM.
Kaiju watches what changes around an account. Twenty holds what sales is seeing inside it. The target integration connects both evidence streams while keeping ownership and pipeline state in Twenty. Bidirectional synchronization is still in development.
Integration in development
In developmentTwenty and Kaiju
Source
Twenty: accounts, people, opportunities, activity
Kaiju
External signals + CRM evidence + account context
Destination
Reviewed signals, evidence, and context back in Twenty
- Current direction
- Bidirectional target; integration in development
- Cadence
- Record changes + reconciliation target
CRM evidence
Give seller activity a precise place in the account record.
Hiring, technology, leadership, and company changes can put an account on the radar. Replies, meetings, new stakeholders, and opportunity movement reveal what happens next. Twenty can add that first-party evidence without treating every CRM field as a signal.
- 01
Keep the CRM record intact
Preserve Twenty IDs, owners, relationships, pipeline state, and seller-maintained fields while Kaiju adds its own evidence and interpretations.
- 02
Use record changes as evidence
Opportunity transitions, stakeholder changes, notes, tasks, and other supported activity stay dated. Kaiju decides which changes satisfy a signal definition.
- 03
Put useful context back in Twenty
Return approved signals, evidence links, and Kaiju-owned context through explicit mappings once the synchronization path is ready.
Signal discipline
Preserve the event before interpreting its sales meaning.
- A CRM field is state. A dated record change can be evidence. A Kaiju signal requires a signal definition to interpret that evidence.
- Keep the Twenty object, record ID, changed fields, event time, and source alongside change events used in signal evaluation.
- Use reconciliation reads alongside webhooks so missed or delayed event delivery does not become permanent account-state drift.
- Keep external evidence, CRM evidence, Kaiju interpretations, and seller-maintained truth distinguishable.
Ownership
Protect seller-maintained fields and explicit write mappings.
- Begin with the minimum read scope needed to resolve identity, relationships, and approved evidence fields.
- Use scoped Twenty API roles and verify webhook signatures before accepting record-change events.
- Write only Kaiju-owned fields, custom objects, or explicitly mapped destinations.
- Keep bidirectional sync labeled in development until reconciliation, webhook ingestion, writeback, retries, and conflict behavior are proven end to end.
Target loop
Twenty records → evidence → signals → action → new CRM evidence.
01
Connect the records your team already uses
Map the Companies, People, Opportunities, relationships, and fields Kaiju is allowed to read or write.
02
Keep CRM changes dated and attributable
Capture current state and supported record changes with the source record, event time, and changed fields attached.
03
Combine CRM activity with outside signals
Evaluate first-party activity beside Kaiju research to update Intent, Mobilization, Progression, filters, and Dynamic Lists.
04
Return the context a seller can use
Write only approved Kaiju-owned context back to Twenty. New CRM activity becomes evidence for the next evaluation.
Data contract
Separate CRM truth, Kaiju evidence, and shared sales context.
Notes, Tasks, and supported activity
- Direction
- Twenty → Kaiju
- Cadence
- Mapped records + change events
- Purpose
- First-party context that can support an account interpretation when its meaning and timestamp are clear.
Record create/update/delete events
- Direction
- Twenty → Kaiju
- Cadence
- Webhook target
- Purpose
- Change evidence for transitions, new participants, removed state, and other monitored CRM events.
Kaiju-owned context
- Direction
- Kaiju → Twenty
- Cadence
- After evaluation + explicit mapping
- Purpose
- Current signal state, why-now context, evidence links, freshness, Dynamic List context, or reviewed next actions.
Sales outcomes
- Direction
- Twenty → Kaiju
- Cadence
- As mapped opportunity or activity state changes
- Purpose
- Outcome evidence for evaluating signal definitions and ranking quality without collapsing buyer readiness into a universal score.
Related solutions
Use Twenty with a defined domain-enrichment workflow.
The integration page explains how reviewed records move. These solutions explain how teams apply the enriched fields after review.
Twenty
Show us how your team uses Twenty.
Bring a real account or opportunity workflow. We’ll use it to decide which records, changes, signals, and seller actions the integration needs to support.