Native integrations #16735
Replies: 8 comments 3 replies
|
Has anyone worked on WeChat and Line integrations (webhooks) ? |
|
Not yet, I tried to implement Whatsapp integration with webhooks (as using any unofficial solution in critical use cases like this is simply too risky) and that's the response I got from core team (#17390 (comment)) so I'd wait a little bit until SDK is stable and v1.0 is released |
|
I would propose on top:
|
|
Google Chat integration seems reasonable as well, since mail, calendar, and contacts are already in the scope. |
|
For native integrations, I would bias toward a thin connector contract first and keep provider-specific sync logic behind workers. That makes it possible to ship integrations incrementally without coupling each provider to the CRM object model. A minimal shape could be: type IntegrationConnector = {
provider: 'linkedin' | 'whatsapp' | 'n8n';
capabilities: Array<'oauth' | 'webhook' | 'polling' | 'bulkSync'>;
mapEvent(event: ProviderEvent): Promise<TwentyMutation[]>;
};Then the app layer only needs to persist auth, enqueue provider events, and apply idempotent |
|
Yes, i think that is a good point, we can build native integration using the same app structure |
|
Hey All, some gaps here I wanted to surface. @FelixMalfait and I chatted on Friday (5/29/2026) and these came up. I would think these categories should be the highest priority for a CRM product because they are actually core to the sales motion. I see a huge list of communications tools above that I rarely see companies using to sell their products.....but every company I know that sells things, uses phone calls and web meetings to actually sell their products! :) Add on here Web Meetings: pull the meeting title, description, date-time, participants, transcript and recording file/link
Add on here VOIP/Telephone/SMS integrations: pull the date-time, participants, transcript and recording file/link
I wanted to also upvote a couple i saw in the lists above that are big winners in my book: - Posthog integration - this one is critical for us, one of the issues blocking leaving hubspot is the analytics tracking that integrates cleanly to the hubspot CRM so you can easily see the pageviews a contact has triggered which gives context to the sales phone call |
|
Something like Fellow.ai as well for meeting transcripts. |
|
Adding a practitioner's perspective from a financial-services / insurance brokerage evaluating Twenty to replace a legacy CRM. Strong +1 on @benweissbehavehealth's phone + web-meeting point. That matches our reality: the actual sales and service motion runs on calls and meetings, not chat apps. Pulling call/meeting date-time, participants, transcript, and recording onto the contact timeline is the highest-value integration category for us. We run Zoom Phone and Zoom Meetings daily, so both are top of our list too. One gap I don't see anywhere in this thread: Microsoft Entra ID / M365 SSO. The auth section lists Okta, Keycloak, and authentik, and OneDrive appears under storage, but Microsoft is missing as an identity provider. For any business running Microsoft 365 (most SMBs we work with), Entra ID SSO is close to table-stakes for adoption. Standard OIDC, broadly useful, not vertical-specific. In line with @suzunn's connector-contract idea: compliance-heavy industries (insurance, wealth, healthcare) increasingly run meeting-intelligence tools that emit call summaries and structured notes. These fit the same "pull transcript/summary onto the timeline" shape, and as thin connectors they're a natural plugin rather than core work, so the pattern matters more than any specific vendor. Not asking for anything vertical-specific to be prioritized, just adding real-world weight to phone/meetings and surfacing the Microsoft SSO gap. Thanks @BOHEUS for maintaining this. |
|
I see two big gaps rich "Caller integrations". |
|
Rocket chat is super popular among self hosted teams. But it's for internal communication (mostly). But this is for internal communication, we are talking bout client's here... I would just build some "chat event system" and "messager api" inside twenty and make it generic and open for the developers to (vibe)code their connectors to all sorts of messangers and publish them in Twenty store |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
This document is a collection of different apps "required" to integrate with Twenty (some of them are must-have, some of them are requested by users here, in Github discussions, or in Discord server, some of them are added because why not, if users can save some money because Twenty has native integration with x service, that may be a dealbreaker, although probably rare case)
Work on integrations by core team will start in Q3/Q4 '26 (so that users can easily add integrations to Twenty)
Important
List of integrations
Communication
Authorization
Related to twentyhq/core-team-issues#16
Storage (files)
To let users store/synchronize files from different sources, nested folders would be a requirement if these integrations were yet to be developed
Calendar
CRM
This is mainly for migration to help users move from different CRMs to Twenty
Marketing automation
For syncing from x to Twenty to have same data in both places (which software should be treated as source of truth?)
Documents
Requested by some users, probably should be done once Files are "surfaced"
Middleware
Only supported by community as core team's focus is on native workflows in form of plugins to said middlewares, to be decided considering how fast Twenty changes
Miscellaneous
If you want to add something to this list, feel free to drop a comment
All reactions