n8n has no built-in Twenty node: n8n’s integrations documentation lists none. Twenty is an open-source CRM you can use in the cloud or host yourself, and its custom objects and fields are what most Twenty community nodes are built around. This guide compares them, using the description and README each author publishes on npm and our own download data.
Twenty CRM community nodes
Our Twenty CRM hub lists 15 packages that pass our quality rule, with 784 npm downloads a week between them. The most downloaded, with the description each author gives on npm (weekly npm downloads as of 28 October 2026):
| Package | Weekly downloads | Latest version | Author’s description |
|---|---|---|---|
| @lilremark/n8n-nodes-twenty-dynamic | 366 | 3.0.0 (23 October 2026) | GraphQL node for Twenty with custom database and field support and resource locators |
| n8n-nodes-twenty | 179 | 0.0.5 (6 July 2025) | Call Twenty CRM’s API |
| n8n-nodes-twenty-dynamic | 102 | 2.1.1 (21 February 2026) | GraphQL node for Twenty with custom database and field support and resource locators |
| @blackswampai/n8n-nodes-twentycrm | 74 | 0.1.5 (19 October 2026) | Twenty CRM integration |
| @linkedpromo/n8n-nodes-twenty | 19 | 0.4.14 (6 February 2026) | Twenty CRM, the open-source CRM |
Versions and dates come from the npm registry. Weekly downloads: npm, last 7 days, adjusted for npm outage days.
The twenty-dynamic packages
@lilremark/n8n-nodes-twenty-dynamic, the most downloaded, and n8n-nodes-twenty-dynamic share the same README; the scoped one has its own repository and the newer release (3.0.0 in October 2026). The node reads your Twenty instance’s schema through Twenty’s metadata API and GraphQL, so your custom objects and custom fields show up as normal n8n inputs, with dropdowns for select fields and inputs for compound types such as full names, links, currency, addresses, emails and phones. It supports create, update, delete and upsert in bulk, and per its README can also reach system objects such as attachments that the Twenty interface doesn’t show.
Its Twenty API credential takes an API key, created in Twenty under Settings > Developers > API with Create API Key, and your instance URL: https://api.twenty.com for Twenty Cloud or your own address when self-hosted.
@blackswampai/n8n-nodes-twentycrm
An independent package (its README stresses that it isn’t affiliated with Twenty) that says it is a verified community node, installable from the nodes panel by searching for Twenty CRM. Its action node covers companies, people, opportunities, tasks and notes with create, get, get many, update and delete, a generic Record resource for any standard or custom object, and read-only schema discovery. It also handles signed record-event webhooks. Its README lists Twenty Cloud and self-hosted URLs and regression tests against Twenty 2.9 and 2.35, and asks you never to put API keys or webhook secrets in workflow fields.
Other packages
- n8n-nodes-twenty: covers Twenty’s API resources, from companies and people to calendar events, message channels, favorites and API keys; its last release dates from July 2025.
- @linkedpromo/n8n-nodes-twenty: create, read, update and delete for all resources, bulk operations, upsert on a matching field, webhook triggers for CRM events, automatic retries and support for custom objects.
Check each node page here for the latest release and, where it has one, its GitHub repository for open issues before you build on a package.
How to choose
- A Twenty workspace with custom objects and fields: @lilremark/n8n-nodes-twenty-dynamic, the most installed and most recently released.
- n8n Cloud: @blackswampai/n8n-nodes-twentycrm, which its README says is verified.
- Workflows triggered by Twenty record events: @blackswampai/n8n-nodes-twentycrm or @linkedpromo/n8n-nodes-twenty, both with webhooks.
- An endpoint none of them covers: the HTTP Request node with your Twenty API key.
To install a package on a self-hosted instance, an owner or admin enters its npm name in Settings > Community Nodes; full steps are in How to Install n8n Community Nodes. On n8n Cloud only verified community nodes can be installed, see Verified vs Unverified n8n Community Nodes. Similar guides: Kommo CRM and Bitrix24.
FAQ
Does n8n have a Twenty CRM node?
Not a built-in one. Twenty support comes from community nodes, or from calling Twenty’s API with the HTTP Request node.
How do I connect n8n to Twenty?
Create an API key in Twenty under Settings > Developers > API, then add it to a Twenty credential in n8n together with your instance URL (https://api.twenty.com for Twenty Cloud).
Can n8n work with custom objects in Twenty?
Yes. The twenty-dynamic packages discover custom objects and fields from your instance, and @blackswampai/n8n-nodes-twentycrm has a generic Record resource for custom objects.
What is the most used Twenty CRM community node?
@lilremark/n8n-nodes-twenty-dynamic, with 366 weekly npm downloads on 28 October 2026.
