4
Add Messagers API
Source: twentyhq/twenty#22977 · opened by @EgorZakharov97
Scope & Context Twenty CRM currently receives contact events only from email providers. While this works well for email communication, many businesses primarily communicate through messaging platforms. The contact event system should become communication-channel agnostic by introducing a generic messaging API that allows any messaging platform to integrate with Twenty through apps/connectors. The goal is to make messenger support extensible instead of implementing every platform inside the core application. Third-party developers should be able to build connectors for platforms such as WhatsApp, Telegram, Signal, WeChat, Facebook Messenger, Instagram Direct, Slack, Microsoft Teams, Discord, Line, Viber, SMS providers, and custom messaging systems. Current behavior CRM gets contact events only from emails. Users can connect email accounts, synchronize conversations, and view email activity inside the contact timeline. There is currently no generic infrastructure for messenge…
No pledges yet. Be the first to back this.
Comments
Similar requests
I created a Twenty MCP Server - Looking for Feedback!
3 votes · 0 comments
Name custom field (middle name, prefix, suffix)
1 vote · 0 comments
Workflow step mutations are unreachable via workspace API keys (`Forbidden resource`); also hidden from GraphQL introspection
0 votes · 0 comments
[Workflow] API keys variables
1 vote · 0 comments
Mandatory Fields
6 votes · 0 comments
No comments yet.