twenty-crm

Automate Twenty CRM workflows via OpenAPI specs and metadata sync.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/leto-labs/openclaw-bootstrap-config --skill twenty-crm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: twenty-crm
Source: https://github.com/leto-labs/openclaw-bootstrap-config/tree/main/skills/twenty-crm
Command: npx skills add https://github.com/leto-labs/openclaw-bootstrap-config --skill twenty-crm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, python3, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Coordinating Twenty CRM operations across core records and workspace metadata can be error-prone and time-consuming when done manually; this Skill provides a structured, API-first approach to keep core and metadata in sync, reducing drift and enabling repeatable automation.

Core Features & Use Cases

  • Baseline-first CRM task execution using OpenAPI core and metadata specs to handle standard record operations efficiently.
  • Metadata drift detection and automatic resync to refresh schemas after changes to objects, fields, views, or layouts.
  • End-to-end guidance for syncing, validating, and applying metadata changes across different workspaces and environments.

Quick Start

Run a baseline sync to refresh core and metadata specs after a metadata change.

Frequently Asked Questions about twenty-crm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Twenty CRM workflows using OpenAPI specs?

Automate Twenty CRM workflows by driving API-first operations through baseline OpenAPI specs. This approach coordinates core record operations and metadata synchronization to reduce manual errors and drift. It fetches and validates core and metadata specs to execute repeatable tasks.

What is metadata drift detection in CRM workspace schemas?

Metadata drift detection in CRM workspace schemas identifies changes to objects, fields, views, or layouts. This Skill performs automatic resync to refresh schemas after metadata changes, keeping workspace schema aligned via drift-aware sync workflows across different environments.

How do I sync metadata changes across multiple Twenty CRM workspaces?

Sync metadata changes across Twenty CRM workspaces using drift-aware workflows that fetch and refresh core and metadata OpenAPI specs. The process validates results and provides end-to-end guidance for applying metadata changes across different workspaces and environments.

Do I need curl and python3 to run CRM metadata synchronization tasks?

Yes, curl and python3 are required dependencies to run CRM metadata synchronization tasks. These tools execute the scripts that fetch baseline OpenAPI specs, validate results, and apply drift-aware resync workflows for managing CRM records and metadata.

Can I manage custom objects and fields in Twenty CRM through API operations?

Manage custom objects and fields in Twenty CRM through API-first operations driven by OpenAPI metadata specs. The Skill handles querying and updating CRM records while keeping workspace schema aligned, applying metadata changes for objects, fields, views, and layouts.

When should I run a baseline sync for Twenty CRM metadata?

Run a baseline sync for Twenty CRM metadata immediately after any metadata change to refresh core and metadata OpenAPI specs. This prevents workspace schema drift and ensures subsequent API operations validate against the current workspace configuration.