twenty-omnichannel-support 0.3.0-beta.21 → 0.3.0-beta.23

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
@@ -11,7 +11,7 @@ Omnichannel Support gives your team a place to follow support cases, read messag
11
11
  - **Update conversations through the API.** Set the title, type, category, status, standard/custom tags, follow-up and other metadata whenever a new message arrives; preserve call recordings and transcriptions.
12
12
  - **Open history from People.** Find related conversations and channel identities in the Omnichannel tab on a Person.
13
13
  - **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.
14
- - **Use your team's knowledge.** Maintain FAQs with configurable scope tags (GENERAL, VERANO, etc.) so each bot retrieves only published answers relevant to its audience; review automated replies before or after they are sent.
14
+ - **Manage FAQs visually.** Open Omnichannel → FAQs for grouped cards, filters, an inline editor and publication controls. Use FAQs (tabla) to access Twenty's original record interface. Maintain FAQs with configurable scope tags (GENERAL, VERANO, etc.) so each bot retrieves only published answers relevant to its audience; review automated replies before or after they are sent.
15
15
  - **See what needs attention.** Choose which KPIs to show in the workspace summary, and create additional graphs and dashboards with Twenty's native editor.
16
16
 
17
17
  WhatsApp integrations can associate number-based JIDs and LIDs with the same customer identity when the provider supplies reliable matching information.
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 the title, type, category, status, standard/custom tags, follow-up and other metadata whenever a 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 with configurable scope tags (GENERAL, VERANO, etc.) so each bot retrieves only published answers relevant to its audience; 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## Conversation types and FAQ scopes\n\nA conversation's **Type** uses a workspace-managed catalog, just like **Category**. When the API receives an unknown `conversation.typeCode` or `conversation.categoryCode`, it creates a record with identical name and code in that workspace, then links it to the conversation. Existing entries are reused without changing their names or settings; disabled entries stay disabled. Existing tags and statuses remain available, and the ingestion endpoint updates only the metadata explicitly supplied on each new message.\n\nFAQs have an independent multi-value **Scope** field. For example, a summer bot may fetch FAQs scoped to GENERAL or VERANO, while skipping other scopes and draft FAQs. Scope filtering is an integration rule, not a replacement for workspace access controls.\n\n## Search approved FAQs from a bot\n\nYour bot can ask the authenticated `POST /s/omnichannel/v1/faqs/search` endpoint a natural-language question and receive a short list of relevant approved answers. The search is deterministic and works across Spanish and Catalan, including FAQ variants, accented query spellings and common equivalents. It uses no LLM, embedding provider or separate database.\n\nEach request can specify `scopeTags` (for example `[\"VERANO\"]`) alongside the question. `GENERAL` is always included; if omitted, the scope filter is restricted to `GENERAL` alone. The endpoint reuses Twenty's workspace Bearer authentication and has no bot secrets or bot registry. Scope tags are query filters, not authorization boundaries: a valid client can request other scopes. See [API reference](docs/API_REFERENCE.md) and [n8n integration](docs/INTEGRACION_N8N.md).\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 the title, type, category, status, standard/custom tags, follow-up and other metadata whenever a 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- **Manage FAQs visually.** Open Omnichannel → FAQs for grouped cards, filters, an inline editor and publication controls. Use FAQs (tabla) to access Twenty's original record interface. Maintain FAQs with configurable scope tags (GENERAL, VERANO, etc.) so each bot retrieves only published answers relevant to its audience; 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## Conversation types and FAQ scopes\n\nA conversation's **Type** uses a workspace-managed catalog, just like **Category**. When the API receives an unknown `conversation.typeCode` or `conversation.categoryCode`, it creates a record with identical name and code in that workspace, then links it to the conversation. Existing entries are reused without changing their names or settings; disabled entries stay disabled. Existing tags and statuses remain available, and the ingestion endpoint updates only the metadata explicitly supplied on each new message.\n\nFAQs have an independent multi-value **Scope** field. For example, a summer bot may fetch FAQs scoped to GENERAL or VERANO, while skipping other scopes and draft FAQs. Scope filtering is an integration rule, not a replacement for workspace access controls.\n\n## Search approved FAQs from a bot\n\nYour bot can ask the authenticated `POST /s/omnichannel/v1/faqs/search` endpoint a natural-language question and receive a short list of relevant approved answers. The search is deterministic and works across Spanish and Catalan, including FAQ variants, accented query spellings and common equivalents. It uses no LLM, embedding provider or separate database.\n\nEach request can specify `scopeTags` (for example `[\"VERANO\"]`) alongside the question. `GENERAL` is always included; if omitted, the scope filter is restricted to `GENERAL` alone. The endpoint reuses Twenty's workspace Bearer authentication and has no bot secrets or bot registry. Scope tags are query filters, not authorization boundaries: a valid client can request other scopes. See [API reference](docs/API_REFERENCE.md) and [n8n integration](docs/INTEGRACION_N8N.md).\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": "43ed86e3f7b69f22ddd7272a4f7abc0c",
17
+ "packageJsonChecksum": "aa0df104388f76577af2e1212dd140ca",
18
18
  "requiredServerVersionRange": ">=2.50.0 <2.51.0",
19
19
  "frontComponentSharedDependencies": {
20
20
  "dependencies": [
@@ -2450,7 +2450,7 @@
2450
2450
  "handlerName": "default.config.handler",
2451
2451
  "sourceHandlerPath": "src/logic-functions/omnichannel-faq-search.logic-function.ts",
2452
2452
  "builtHandlerPath": "src/logic-functions/omnichannel-faq-search.logic-function.mjs",
2453
- "builtHandlerChecksum": "b4d29ef9516a498f9f3d96828d355894"
2453
+ "builtHandlerChecksum": "9feb5fad5d8084065f31a7f778c8bc30"
2454
2454
  },
2455
2455
  {
2456
2456
  "universalIdentifier": "b0a4d933-0a5f-4c8d-b513-ae9f3702451b",
@@ -2464,7 +2464,7 @@
2464
2464
  "handlerName": "default.config.handler",
2465
2465
  "sourceHandlerPath": "src/logic-functions/omnichannel-ingest.logic-function.ts",
2466
2466
  "builtHandlerPath": "src/logic-functions/omnichannel-ingest.logic-function.mjs",
2467
- "builtHandlerChecksum": "a2142256b691f9c177c4266967d2a0d4"
2467
+ "builtHandlerChecksum": "8cffa49d7536022f29ce69de2684e71f"
2468
2468
  }
2469
2469
  ],
2470
2470
  "frontComponents": [
@@ -2475,7 +2475,7 @@
2475
2475
  "componentName": "Overview",
2476
2476
  "sourceComponentPath": "src/front-components/support-overview.tsx",
2477
2477
  "builtComponentPath": "src/front-components/support-overview.mjs",
2478
- "builtComponentChecksum": "a1c36b0e3fc4811fa02c7bbc3ae6f04fcadd330d8b4be2e77623038056ee89b8",
2478
+ "builtComponentChecksum": "25f284502cf7306a2eccc285ef57bf13a6cdb9cc59c27a9bf15346d4edc7bc95",
2479
2479
  "isHeadless": false,
2480
2480
  "usesSdkClient": false
2481
2481
  },
@@ -2486,7 +2486,7 @@
2486
2486
  "componentName": "ChannelPolicies",
2487
2487
  "sourceComponentPath": "src/front-components/channel-policies.tsx",
2488
2488
  "builtComponentPath": "src/front-components/channel-policies.mjs",
2489
- "builtComponentChecksum": "c4e492ac2721b805ebfac793af7e28e2bb067595f6d5ff5b325e3f7a25780e8d",
2489
+ "builtComponentChecksum": "ca32241646c3144d8db9469898af36f7fc3b25c44e914116cbb6726ede587775",
2490
2490
  "isHeadless": false,
2491
2491
  "usesSdkClient": false
2492
2492
  },
@@ -2503,7 +2503,18 @@
2503
2503
  "componentName": "FaqScopeEditor",
2504
2504
  "sourceComponentPath": "src/front-components/faq-scope-editor.tsx",
2505
2505
  "builtComponentPath": "src/front-components/faq-scope-editor.mjs",
2506
- "builtComponentChecksum": "21e22b9babdf899be7d07b0615bf0ce90598bb03085a9df2444b8e8a0141bbf4",
2506
+ "builtComponentChecksum": "496113a7c1d35ef251a2051e3e8ca1730ab0af4a3d810ca5d80d12e7a8785f4f",
2507
+ "isHeadless": false,
2508
+ "usesSdkClient": false
2509
+ },
2510
+ {
2511
+ "universalIdentifier": "9fb4c079-87e0-485c-8ce1-37c145e29501",
2512
+ "name": "faq-manager",
2513
+ "description": "Gestión visual de preguntas frecuentes con categorías, filtros y editor.",
2514
+ "componentName": "FaqManager",
2515
+ "sourceComponentPath": "src/front-components/faq-manager.tsx",
2516
+ "builtComponentPath": "src/front-components/faq-manager.mjs",
2517
+ "builtComponentChecksum": "3296ff1583b1ea3b35e067209253bf4aad3939ec2cb2c6a486b08aca9f5c5d61",
2507
2518
  "isHeadless": false,
2508
2519
  "usesSdkClient": false
2509
2520
  },
@@ -2514,7 +2525,7 @@
2514
2525
  "componentName": "ChannelSetup",
2515
2526
  "sourceComponentPath": "src/front-components/channel-setup.tsx",
2516
2527
  "builtComponentPath": "src/front-components/channel-setup.mjs",
2517
- "builtComponentChecksum": "ce83735a9623bcf1018343676141831bba132845afa73bac2edf32d1c0a55b33",
2528
+ "builtComponentChecksum": "71cf750d2c328fd310ccccf5e31b29ac5490acc53d5123c7768c7e61bc2ef609",
2518
2529
  "isHeadless": false,
2519
2530
  "usesSdkClient": false
2520
2531
  },
@@ -2531,7 +2542,7 @@
2531
2542
  "componentName": "CaseTimeline",
2532
2543
  "sourceComponentPath": "src/front-components/case-timeline.tsx",
2533
2544
  "builtComponentPath": "src/front-components/case-timeline.mjs",
2534
- "builtComponentChecksum": "fd02d72c1d3332ea14afcb650990589272f7fd0936ab6e86b302adf20c3e36b1",
2545
+ "builtComponentChecksum": "f5be8c729403423f0d4f1685d4aa9192a1f362079131f326f98e86f89b8b44ba",
2535
2546
  "isHeadless": false,
2536
2547
  "usesSdkClient": false
2537
2548
  }
@@ -3158,9 +3169,9 @@
3158
3169
  },
3159
3170
  {
3160
3171
  "universalIdentifier": "0f7e43b6-8d2f-5bee-94b8-528ac0c88726",
3161
- "name": "FAQs",
3162
- "icon": "IconBook",
3163
- "position": 3,
3172
+ "name": "FAQs (tabla)",
3173
+ "icon": "IconTable",
3174
+ "position": 3.5,
3164
3175
  "type": "OBJECT",
3165
3176
  "targetObjectUniversalIdentifier": "b6cbc813-9e97-5b66-a4dd-28070f441fa3",
3166
3177
  "folderUniversalIdentifier": "b8a93978-47b6-5d6a-999e-a6e71902c79f"
@@ -3210,6 +3221,15 @@
3210
3221
  "targetObjectUniversalIdentifier": "232da773-0bcf-5da3-9ba7-a6040e9918e2",
3211
3222
  "folderUniversalIdentifier": "b8a93978-47b6-5d6a-999e-a6e71902c79f"
3212
3223
  },
3224
+ {
3225
+ "universalIdentifier": "84de8680-4e40-42b8-b3c7-7120b050cb54",
3226
+ "name": "FAQs",
3227
+ "icon": "IconBook",
3228
+ "position": 3,
3229
+ "type": "PAGE_LAYOUT",
3230
+ "pageLayoutUniversalIdentifier": "c6022bb8-4f47-43d9-a7a9-9fe834190c56",
3231
+ "folderUniversalIdentifier": "b8a93978-47b6-5d6a-999e-a6e71902c79f"
3232
+ },
3213
3233
  {
3214
3234
  "universalIdentifier": "b8a93978-47b6-5d6a-999e-a6e71902c79f",
3215
3235
  "name": "Omnichannel",
@@ -3681,6 +3701,32 @@
3681
3701
  }
3682
3702
  ]
3683
3703
  },
3704
+ {
3705
+ "universalIdentifier": "c6022bb8-4f47-43d9-a7a9-9fe834190c56",
3706
+ "name": "Gestión visual de FAQs",
3707
+ "type": "STANDALONE_PAGE",
3708
+ "tabs": [
3709
+ {
3710
+ "universalIdentifier": "f01da1ce-f4a8-42cf-9cd7-1ce3da2a21ba",
3711
+ "title": "FAQs",
3712
+ "icon": "IconBook",
3713
+ "position": 0,
3714
+ "layoutMode": "VERTICAL_LIST",
3715
+ "widgets": [
3716
+ {
3717
+ "universalIdentifier": "e6310f10-b5d1-4cf5-9824-7c9ab61dd1fa",
3718
+ "title": "Gestión de FAQs",
3719
+ "type": "FRONT_COMPONENT",
3720
+ "heightBehavior": "TAB_VIEWPORT",
3721
+ "configuration": {
3722
+ "configurationType": "FRONT_COMPONENT",
3723
+ "frontComponentUniversalIdentifier": "9fb4c079-87e0-485c-8ce1-37c145e29501"
3724
+ }
3725
+ }
3726
+ ]
3727
+ }
3728
+ ]
3729
+ },
3684
3730
  {
3685
3731
  "universalIdentifier": "ca10d0b1-ec11-4d12-8c30-33ad80040012",
3686
3732
  "name": "Configuración de canales",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "twenty-omnichannel-support",
3
- "version": "0.3.0-beta.21",
3
+ "version": "0.3.0-beta.23",
4
4
  "description": "Customer support cases, conversations and channel policies for Twenty CRM",
5
5
  "license": "MIT",
6
6
  "type": "module",