By twentyhq

Guides changes to an existing Twenty app: adding or editing objects, layouts, logic functions and front components, with a plan stated before multi-entity edits.

twentyhq/twenty

Operates an existing Twenty app: managing remotes, syncing, building, deploying, reading logs, running tests and setting up CI/CD, with confirmation for production.

twentyhq/twenty

Contributor guide for step three of adding a syncable entity to the Twenty server: write the validator, the migration action builder and the orchestrator wiring.

twentyhq/twenty

Walks through step 2 of adding a syncable entity to the Twenty server: a cache service for flat entity maps and utilities that transform entities and DTOs into universal flat entities.

twentyhq/twenty

Registers a new syncable entity in three NestJS modules and adds its service and GraphQL resolver layers when contributing to the Twenty server.

twentyhq/twenty

Step four of adding a syncable entity in the Twenty server: write create, update and delete action handlers that run workspace migrations against the database.

twentyhq/twenty

Step-by-step guide to writing the mandatory integration tests for syncable metadata entities in Twenty's server, covering failures and CRUD success cases.

twentyhq/twenty

Walks through the first of six steps for adding a syncable entity to Twenty's server: metadata name, TypeORM entity, flat types and central constants.

twentyhq/twenty

Starts a new Twenty app project, first settling which Twenty instance it will sync to: an existing server you point at, or a disposable local one run through Docker.

twentyhq/twenty

Prepares a Twenty app for npm or marketplace release: package metadata, defineApplication listing fields, README and About copy, logo, screenshots and public assets.

twentyhq/twenty

Browser QA for a pull request against a running Twenty app: scenarios drawn from the diff, run in a real browser, checked in the database and logs, and closed with a verdict and report.

twentyhq/twenty

Retrieves Twenty CRM records through the connected MCP server and presents them as readable summaries or tables with working record links instead of raw API output.

twentyhq/twenty

Connects the agent to an existing Twenty workspace through MCP to read records and metadata, and presents CRM data as readable Markdown with links instead of raw API output.

twentyhq/twenty