An independent community integration for Twenty CRM. Read and write standard or custom records, discover schema metadata, and receive signed record events.
Company, Person, Opportunity, Task, and Note have focused record actions. Record provides generic actions for active standard or custom objects. Schema Object exposes read-only discovery.
Metadata-driven field mapping follows the connected workspace. Fixed-resource reads and JSON-input writes use explicit routes; generic records and field mapping require metadata access. Record mutations are not automatically retried.
The trigger requires manual webhook registration in Twenty. It verifies an HMAC-SHA256 signature over the raw body and signed timestamp, with a five-minute tolerance. It can filter to one object or accept all objects. Unsigned delivery is not supported.
| Resource | Operations |
|---|---|
| Company | Create, Delete, Get, Get Many, Update |
| Person | Create, Delete, Get, Get Many, Update |
| Opportunity | Create, Delete, Get, Get Many, Update |
| Task | Create, Delete, Get, Get Many, Update |
| Note | Create, Delete, Get, Get Many, Update |
| Record | Create, Delete, Get, Get Many, Update |
| Schema Object | Get, Get Many |
Twenty CRM Trigger receives Record Created, Record Updated, and Record Deleted events. Register the correct test or production URL in Twenty and configure the same secret on both sides.
Reviewed 2026-09-07 against release source 5eabd21. See the repository for tests and detailed limitations.
This workflow runs manually to search OpenMart for local businesses in a chosen niche and location, then imports only new companies into Twenty CRM based on website domain matching and creates a follow-up review task for each newly created prospect.
This workflow checks Prometheus-style infrastructure metrics in OpenObserve on a schedule, detects sustained pressure based on coverage and threshold rules, and then creates or updates a matching review task in Twenty CRM with evidence from the latest and previous time windows.
This workflow triggers on new Twenty CRM custom supportCase records, applies an urgent or standard SLA based on priority, creates or reuses a deterministic owner task, and updates the support case with triage metadata for replay-safe escalation.
This workflow captures consultation requests from an n8n Form, logs the raw submission in Twenty CRM, normalizes and scores the lead, deduplicates Companies by website and People by work email, and then creates either a qualified Opportunity with a follow-up Task or a nurture-review Task.