Add Messagers API

[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 messenger conversations.

Expected behavior

Introduce a generic Messaging Provider API that works similarly to the existing email integration.

Users should be able to install a messaging connector, authenticate their account, and communicate with contacts directly from Twenty.

Authentication

Each messaging connector should provide its own authentication flow.

Users should be able to:

• Install a messaging app/connector
• Authenticate their account (OAuth, QR code, API key, etc.)
• Manage multiple connected messaging accounts

The experience should be similar to connecting an email account today.

Contact Timeline

Messaging providers should publish events into the existing contact event system.

Examples include:

• Message sent
• Message received
• Attachment received
• Conversation started
• Delivery status
• Read status (where supported)

These events should appear in the contact timeline alongside emails.

Contact Chat

Each contact should have a Chat button that opens a conversation panel.

From this panel, users should be able to:

• Select one of their connected messaging accounts
• View conversation history
• Send and receive messages
• Switch between different messaging providers for the same contact

Workflow Support

Messaging should also be available inside Workflows.

Examples include:

• Send message
• Reply to last conversation
• Send template message
• Send attachment

This enables use cases such as:

• Automatic follow-ups
• Appointment reminders
• Order notifications
• Customer support automation
• Mass messaging campaigns

Benefits

• Makes Twenty a communication hub instead of an email-only CRM.
• Allows the community to build integrations for any messaging platform without waiting for core implementation.
• Provides a consistent communication experience regardless of channel.
• Enables workflow automation based on messaging events in addition to email.
• Makes the messaging ecosystem fully extensible through apps/connectors.

[orobosoft]

This is highly important... I would be super elated if this is done this year.

[ManasMadrecha]

Supporting custom email provider (e.g., aws ses, mailerlite, postmarkapp, mailgun, etc.), whatsapp official api, whatsapp unofficial api (e.g., available in gohighlevel apps), instagram DM - these should be priority for making it truly full-fledged crm (marketing + sales).

[BOHEUS]

Custom email providers are supported as long as they support IMAP/SMTP protocols, native email campaigns are coming soon to Twenty, WhatsApp will be added to Twenty in the future with official API (there's no room for unofficial API), same with Instagram