twenty-omnichannel-support 0.3.0-beta.13 → 0.3.0-beta.14

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -29,6 +29,10 @@ Omnichannel Support does not include a messaging gateway or an AI service. If yo
29
29
  3. In **Conversation management**, choose how messages should be grouped into cases.
30
30
  4. Connect your provider to n8n and call the app's authenticated ingestion API. Test an incoming message, a retry and a reply before enabling the channel.
31
31
 
32
+ ## Automatic chat grouping
33
+
34
+ Choose **Automatic grouping** (HYBRID) or **Activity session** (SESSION) in each channel's conversation settings. The ingestion API can append new inbound and outbound messages to the same eligible conversation, including automated notices, without a separate search in n8n. It respects the channel's continuity and reopening windows, never guesses between multiple active cases, and applies `conversation.status` when a new message is recorded.
35
+
32
36
  ## Ingestion API
33
37
 
34
38
  The application exposes an authenticated `POST /s/omnichannel/v1/ingest` endpoint for integrations. It accepts email, WhatsApp, Instagram, Telegram and phone events and handles contact matching, conversation linking and message deduplication inside Twenty. Sending messages still happens through your chosen provider.
package/manifest.json CHANGED
@@ -12,9 +12,9 @@
12
12
  "galleryImages": [
13
13
  "public/cover.generated.png"
14
14
  ],
15
- "aboutDescription": "# Omnichannel Support for Twenty\n\nManage conversations across email, chat and phone channels in Twenty CRM.\n\nOmnichannel Support gives your team a place to follow support cases, read messages in context, and keep track of what still needs attention. Cases live alongside your existing Twenty contacts, so you can see the history of an issue without maintaining a separate support database.\n\n## What you can do\n\n- **Follow each enquiry.** Keep incoming and outgoing messages together, with the case's status, category, owner and resolution.\n- **Work across channels.** Connect email inboxes, WhatsApp, Instagram, Telegram and phone systems separately in each workspace.\n- **Update conversations through the API.** Set status, follow-up, category, language, summary or comments as each new message arrives; preserve call recordings and transcriptions.\n- **Open history from People.** Find related conversations and channel identities in the Omnichannel tab on a Person.\n- **Choose how conversations become cases.** Keep email replies in the same thread, or group chat messages by activity and topic. Each channel has its own settings.\n- **Use your team's knowledge.** Maintain FAQs for connected bots and review automated replies before or after they are sent.\n- **See what needs attention.** Choose which KPIs to show in the workspace summary, and create additional graphs and dashboards with Twenty's native editor.\n\nWhatsApp integrations can associate number-based JIDs and LIDs with the same customer identity when the provider supplies reliable matching information.\n\n## How it connects\n\nThe app stores cases, messages, FAQs and channel settings in Twenty. To receive or send messages, connect your own email or messaging provider through an automation tool such as **n8n**. The app provides a workspace-authenticated ingestion endpoint that receives normalized events and records identities, contacts, cases, messages and delivery status. Your automation tool only needs to connect to the provider and send one HTTP request.\n\nOmnichannel Support does not include a messaging gateway or an AI service. If you use a bot or a classifier, you configure it in your automation tool.\n\n## Get started\n\n1. Install Omnichannel Support from the Twenty Marketplace in your workspace.\n2. Open **Channels** in the support section of Twenty and add the inbox or account you want to connect.\n3. In **Conversation management**, choose how messages should be grouped into cases.\n4. Connect your provider to n8n and call the app's authenticated ingestion API. Test an incoming message, a retry and a reply before enabling the channel.\n\n## Ingestion API\n\nThe application exposes an authenticated `POST /s/omnichannel/v1/ingest` endpoint for integrations. It accepts email, WhatsApp, Instagram, Telegram and phone events and handles contact matching, conversation linking and message deduplication inside Twenty. Sending messages still happens through your chosen provider.\n\n[Read the complete API reference](https://github.com/mikiguillamon/twenty-omnichannel-support/blob/main/docs/API_REFERENCE.md) for endpoints, fields, validation rules, response codes and examples. See the [integration guide](https://github.com/mikiguillamon/twenty-omnichannel-support/blob/main/docs/INTEGRACION_N8N.md) for n8n setup.\n\n## Guides\n\n- [API reference](https://github.com/mikiguillamon/twenty-omnichannel-support/blob/main/docs/API_REFERENCE.md)\n- [Daily operations and conversation statuses](https://github.com/mikiguillamon/twenty-omnichannel-support/blob/main/docs/OPERATIVA.md)\n- [Workspace dashboards](https://github.com/mikiguillamon/twenty-omnichannel-support/blob/main/docs/DASHBOARD.md)\n\n- [Installation and first setup](https://github.com/mikiguillamon/twenty-omnichannel-support/blob/main/docs/INSTALACION.md)\n- [Connecting n8n and Twenty](https://github.com/mikiguillamon/twenty-omnichannel-support/blob/main/docs/INTEGRACION_N8N.md)\n- [Conversation rules for email and chat](https://github.com/mikiguillamon/twenty-omnichannel-support/blob/main/docs/POLITICAS_CONVERSACION.md)\n- [Source code and developer documentation](https://github.com/mikiguillamon/twenty-omnichannel-support)\n\nFree and open source under the [MIT license](https://github.com/mikiguillamon/twenty-omnichannel-support/blob/main/LICENSE).\n\n\n### Personas y llamadas\n\nLa API de ingestión admite `contact.firstName` y `contact.lastName`. Se guardan en el nombre nativo de la Persona de Twenty y, cuando se identifica de forma segura una Persona existente, se completan los campos vacíos sin sobrescribir los datos que ya tenga.\n\nLos canales `PHONE` registran llamadas y sus transcripciones. Una `message.callRecordingUrl` HTTPS se muestra con reproductor de audio en el historial de la conversación; no hace falta adjuntar el archivo a Twenty. Para mantener los audios protegidos, almacénalos en un servicio con control de acceso y revisa la caducidad de sus enlaces. Consulta [API reference](docs/API_REFERENCE.md) para el contrato completo.\n",
15
+ "aboutDescription": "# Omnichannel Support for Twenty\n\nManage conversations across email, chat and phone channels in Twenty CRM.\n\nOmnichannel Support gives your team a place to follow support cases, read messages in context, and keep track of what still needs attention. Cases live alongside your existing Twenty contacts, so you can see the history of an issue without maintaining a separate support database.\n\n## What you can do\n\n- **Follow each enquiry.** Keep incoming and outgoing messages together, with the case's status, category, owner and resolution.\n- **Work across channels.** Connect email inboxes, WhatsApp, Instagram, Telegram and phone systems separately in each workspace.\n- **Update conversations through the API.** Set status, follow-up, category, language, summary or comments as each new message arrives; preserve call recordings and transcriptions.\n- **Open history from People.** Find related conversations and channel identities in the Omnichannel tab on a Person.\n- **Choose how conversations become cases.** Keep email replies in the same thread, or group chat messages by activity and topic. Each channel has its own settings.\n- **Use your team's knowledge.** Maintain FAQs for connected bots and review automated replies before or after they are sent.\n- **See what needs attention.** Choose which KPIs to show in the workspace summary, and create additional graphs and dashboards with Twenty's native editor.\n\nWhatsApp integrations can associate number-based JIDs and LIDs with the same customer identity when the provider supplies reliable matching information.\n\n## How it connects\n\nThe app stores cases, messages, FAQs and channel settings in Twenty. To receive or send messages, connect your own email or messaging provider through an automation tool such as **n8n**. The app provides a workspace-authenticated ingestion endpoint that receives normalized events and records identities, contacts, cases, messages and delivery status. Your automation tool only needs to connect to the provider and send one HTTP request.\n\nOmnichannel Support does not include a messaging gateway or an AI service. If you use a bot or a classifier, you configure it in your automation tool.\n\n## Get started\n\n1. Install Omnichannel Support from the Twenty Marketplace in your workspace.\n2. Open **Channels** in the support section of Twenty and add the inbox or account you want to connect.\n3. In **Conversation management**, choose how messages should be grouped into cases.\n4. Connect your provider to n8n and call the app's authenticated ingestion API. Test an incoming message, a retry and a reply before enabling the channel.\n\n## Automatic chat grouping\n\nChoose **Automatic grouping** (HYBRID) or **Activity session** (SESSION) in each channel's conversation settings. The ingestion API can append new inbound and outbound messages to the same eligible conversation, including automated notices, without a separate search in n8n. It respects the channel's continuity and reopening windows, never guesses between multiple active cases, and applies `conversation.status` when a new message is recorded.\n\n## Ingestion API\n\nThe application exposes an authenticated `POST /s/omnichannel/v1/ingest` endpoint for integrations. It accepts email, WhatsApp, Instagram, Telegram and phone events and handles contact matching, conversation linking and message deduplication inside Twenty. Sending messages still happens through your chosen provider.\n\n[Read the complete API reference](https://github.com/mikiguillamon/twenty-omnichannel-support/blob/main/docs/API_REFERENCE.md) for endpoints, fields, validation rules, response codes and examples. See the [integration guide](https://github.com/mikiguillamon/twenty-omnichannel-support/blob/main/docs/INTEGRACION_N8N.md) for n8n setup.\n\n## Guides\n\n- [API reference](https://github.com/mikiguillamon/twenty-omnichannel-support/blob/main/docs/API_REFERENCE.md)\n- [Daily operations and conversation statuses](https://github.com/mikiguillamon/twenty-omnichannel-support/blob/main/docs/OPERATIVA.md)\n- [Workspace dashboards](https://github.com/mikiguillamon/twenty-omnichannel-support/blob/main/docs/DASHBOARD.md)\n\n- [Installation and first setup](https://github.com/mikiguillamon/twenty-omnichannel-support/blob/main/docs/INSTALACION.md)\n- [Connecting n8n and Twenty](https://github.com/mikiguillamon/twenty-omnichannel-support/blob/main/docs/INTEGRACION_N8N.md)\n- [Conversation rules for email and chat](https://github.com/mikiguillamon/twenty-omnichannel-support/blob/main/docs/POLITICAS_CONVERSACION.md)\n- [Source code and developer documentation](https://github.com/mikiguillamon/twenty-omnichannel-support)\n\nFree and open source under the [MIT license](https://github.com/mikiguillamon/twenty-omnichannel-support/blob/main/LICENSE).\n\n\n### Personas y llamadas\n\nLa API de ingestión admite `contact.firstName` y `contact.lastName`. Se guardan en el nombre nativo de la Persona de Twenty y, cuando se identifica de forma segura una Persona existente, se completan los campos vacíos sin sobrescribir los datos que ya tenga.\n\nLos canales `PHONE` registran llamadas y sus transcripciones. Una `message.callRecordingUrl` HTTPS se muestra con reproductor de audio en el historial de la conversación; no hace falta adjuntar el archivo a Twenty. Para mantener los audios protegidos, almacénalos en un servicio con control de acceso y revisa la caducidad de sus enlaces. Consulta [API reference](docs/API_REFERENCE.md) para el contrato completo.\n",
16
16
  "yarnLockChecksum": "78975ce4e8278cf91b403a95399b5b7e",
17
- "packageJsonChecksum": "d61a52dfdf00e24ba3f46997ec386d5b",
17
+ "packageJsonChecksum": "9130496011d12cd87b79d7e6abf373a7",
18
18
  "requiredServerVersionRange": ">=2.50.0 <2.51.0",
19
19
  "frontComponentSharedDependencies": {
20
20
  "dependencies": [
@@ -2350,7 +2350,7 @@
2350
2350
  "handlerName": "default.config.handler",
2351
2351
  "sourceHandlerPath": "src/logic-functions/omnichannel-ingest.logic-function.ts",
2352
2352
  "builtHandlerPath": "src/logic-functions/omnichannel-ingest.logic-function.mjs",
2353
- "builtHandlerChecksum": "24fc67f7c2f3ae5dd6623c5d1fe73e2e"
2353
+ "builtHandlerChecksum": "51ad8655faf80898d8a09295dfa59a54"
2354
2354
  }
2355
2355
  ],
2356
2356
  "frontComponents": [
@@ -2372,7 +2372,7 @@
2372
2372
  "componentName": "ChannelPolicies",
2373
2373
  "sourceComponentPath": "src/front-components/channel-policies.tsx",
2374
2374
  "builtComponentPath": "src/front-components/channel-policies.mjs",
2375
- "builtComponentChecksum": "23cea8bc3d2d4d7c08f167e2c060ff4e52a9644039329c522421a4502b124c52",
2375
+ "builtComponentChecksum": "8906abf22d11e9752010915274a6e5fec3c0ffc680448fffa2accfa67e422389",
2376
2376
  "isHeadless": false,
2377
2377
  "usesSdkClient": false
2378
2378
  },
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "twenty-omnichannel-support",
3
- "version": "0.3.0-beta.13",
3
+ "version": "0.3.0-beta.14",
4
4
  "description": "Customer support cases, conversations and channel policies for Twenty CRM",
5
5
  "license": "MIT",
6
6
  "type": "module",