Twenty

Workflows the agent can manage

• manage contacts and companies
• track sales pipeline
• automate pipeline follow-up
• integrate pipeline data via API/webhooks

Agent operability

Editorial agent-readiness estimate: 4/5. This reflects documented interfaces and proposed workflows, not a successful installation or a support promise. Assessment date not recorded; verify upstream documentation before use.

• REST — REST API for records and pipeline data
• GRAPHQL — GraphQL API for records and pipeline data
• WEBHOOKS — Webhooks for record/pipeline events

Evidence consulted

• Official repository documents self-hosting via Docker Compose with PostgreSQL and Redis. [stated; https://github.com/twentyhq/twenty]
• Official self-hosting documentation publishes a 2 GB RAM minimum. [stated; https://twenty.com/developers/local-setup]
• Official developer documentation describes REST and GraphQL APIs plus webhooks. [stated; https://twenty.com/developers]

Implementation notes

Use as the consultancy's primary customer/pipeline record; confirm current self-host resource guidance and only connect inbox/calendar integrations the customer actually wants automated.

Licence / edition: AGPL-3.0; verify current upstream terms before commercial hosted use. Confirm current self-host feature parity against any hosted/paid plan before relying on a specific capability.

Resources: standard class — Official self-host documentation currently publishes a 2 GB RAM minimum; production sizing depends on data volume and worker/queue load. (stated)

External prerequisites: OAuth credentials for connected inboxes/calendars where that integration is used

Security: Catalogue qualification is not a security certification; inspect current advisories, supported versions and deployment guidance before setup.