67 Commits

Author	SHA1	Message	Date
Gabriel Jablonski	72c9821270	feat(whatsapp): add emoji reactions UI (#276) ... * feat(whatsapp): add emoji reactions UI Adds end-to-end agent UI for emoji reactions on WhatsApp inboxes (Cloud API, Baileys, Z-API). Reactions arrive as Messages with is_reaction=true; this PR exposes them in the bubble UI and lets agents react with toggle/replace/remove semantics. - Add POST /reactions endpoint with toggle/replace logic that handles multi-device echoes from the same connected number - Add Channel::Whatsapp#supports_reactions? capability - Add Message.hide_removed_reactions scope and use it in conversation card preview / last_non_activity_message - Enrich last_non_activity_message with in_reply_to_snippet for reaction previews in chat list - Frontend: hover EmojiReactionPicker (8 quick + full picker) with alignment-aware positioning, single ReactionDisplay chip aggregating emojis with total count, conversation card preview shows "Você reagiu" for own/multi-device echoes * fix: address CodeRabbit review feedback - MessagePreview: render "Você" for outgoing reaction echoes that have no sender (multi-device echoes from the connected number) - MessagesView#findCurrentUserReaction: prefer active reactions over deleted rows so a stale deleted echo cannot hijack the toggle target - conversationHelper: drop removed reactions up-front so the activity fallback never returns null when older non-removed messages exist - imap_import rake: wrap IMAP work in begin/ensure so the session is closed even when uid_search/scan_new_email_uids raises - ReactionDisplay: include reaction.id in the user row so v-for keys stay stable across re-renders * fix: address CodeRabbit round 2 feedback - enterprise Message override of mark_pending_conversation_as_open_for_human_response now early-returns on reaction? so reactions can no longer auto-open Captain-pending conversations (matches the OSS guard) - whatsapp incoming reaction-removal handlers (Cloud/Baileys/Z-API) look up the reaction Message globally by sender instead of through the inbound conversation scope, then operate on existing.conversation; otherwise an old/resolved thread could be silently no-op'd while the inbound flow created a stray empty thread - EmojiReactionPicker: localize quick-emoji tooltip labels via i18n keys - Message.vue: track pendingTimeouts and clear them on unmount so the cooldown setTimeout no longer touches state after teardown - toggleMessageReaction action returns the API promise so callers can reconcile if the cable echo is delayed * fix: address CodeRabbit round 3 feedback - MessageFinder#page_window: pluck the 20-row window IDs before taking .min so the latest page honors PAGE_LIMIT (ActiveRecord's .minimum(:id) ignores .limit and aggregates over the whole relation) - ReactionsController#current_user_reaction: rank active reactions ahead of deleted rows (same invariant as the frontend lookup) so a stale deleted echo can no longer hijack the toggle target and resurrect itself - Whatsapp incoming handlers (Cloud, Baileys individual & group, Z-API) now branch on reaction_removal? BEFORE set_conversation / find_or_create_group_ conversation, so a blank reaction-removal webhook can never open or create a stray thread just to no-op - Message#reaction?: strict-boolean cast (via ActiveModel::Type::Boolean) so a stored string "false" no longer leaks through .present? as truthy * fix: address CodeRabbit round 4 feedback - MessageList: anchor unread divider on the filtered visibleMessages (firstUnreadId can land on a reaction that's filtered out, otherwise the separator silently disappears) - ReactionDisplay: render the removable user row as a real <button> when it's the current user's reaction so keyboard users can focus/activate it - MessagesView#findCurrentUserReaction: read sender_type from m.sender_type OR m.sender?.type so REST-loaded messages match the same row instead of spawning a duplicate optimistic reaction - Whatsapp incoming reaction-removal lookup (Cloud, Baileys, Z-API): pick the newest active row first and only fall back to the newest deleted row when no active reaction exists, mirroring the controller invariant - CardMessagePreview: use MESSAGE_TYPE.OUTGOING constant in place of the literal 1 for the multi-device reaction echo check * fix: address CodeRabbit round 5 feedback - ReactionsController#ensure_target_is_reactable: reject activity, template, failed, is_unsupported and missing-source_id targets so the API mirrors the client toolbar gate and refuses reactions that could never land on WhatsApp - MessageList reaction aggregator: treat "agent reacted via Chatwoot" and "agent reacted via the connected phone" as the same self bucket so the chip no longer double-counts the current user when both shapes coexist for one target - internalChat ReactionDisplay: render the removable user row as a real <button> so keyboard users can focus and trigger removal (mirrors the fix already applied to components-next/message/ReactionDisplay) - EventDataPresenter#push_last_non_activity_message: reorder created_at: :desc before .first so the cable snapshot publishes the latest preview instead of the oldest row - Z-API mark_existing_reaction_as_removed: drop the blanket `return unless incoming_message?` and route the lookup by direction (contact sender for incoming removals, senderless outgoing row for multi-device removals from the connected phone). Chatwoot-originated echoes stay idempotent because the active-first guard finds nothing once the controller has flipped deleted=true locally - spec: assert reaction removal does not change messages.count on the in-place Cloud path * fix: address CodeRabbit round 6 feedback - ReactionsController: validate the emoji payload is a single grapheme cluster containing a Unicode Emoji codepoint (not just <=32 bytes), so arbitrary short strings like "ok" or "123" can no longer be persisted as a reaction or enqueued as a WhatsApp reaction send - target_unreactable_error: add the content_attributes['deleted'] guard to mirror the frontend picker gate on deleted messages - IncomingMessageBaseService: move contact_processable? AFTER the reaction_removal? early-return so a blocked contact's removal webhook can still reconcile an existing reaction row instead of leaving a stale chip/preview - imap_import rake: add safe_close_imap(imap) that falls back to disconnect when logout raises Net::IMAP::Error, mirroring terminate_imap_connection in BaseFetchEmailService, and replace the three ensure-block imap&.logout sites with it * fix: address CodeRabbit round 7 feedback - CardMessagePreview: resolve `lastNonActivityMessage` against the live `messages` array by id before rendering, so the chat-card preview picks up the freshest copy instead of the (possibly stale) snapshot that was mutated in place by a reaction toggle / multi-device echo - Message + ReactionDisplay: thread an `inboxSupportsReactions` → `read-only` prop into the chip so non-supported channels (eg. 360Dialog) render historical reactions without a clickable toggle/remove path that would only hit a 422 - conversations/index.js: replace the truthiness `&&` guard around the out-of-order MESSAGE_UPDATED check with `Number.isFinite` parsing so a malformed/missing `updated_at` is treated as stale instead of silently overwriting a fresher local row - Baileys mark_existing_reaction_as_removed: drop the blanket `return unless incoming?` and split the lookup by direction (sender for incoming, sender-less outgoing for multi-device removals) to mirror the Z-API/Cloud handlers - Whatsapp reaction-removal lookup (Cloud, Baileys, Z-API): drop the fallback to the newest deleted row so a Chatwoot-originated removal echo no-ops cleanly instead of bumping `updated_at` and dispatching another `conversation.updated` - conversation jbuilder: explicit `reorder(created_at: :desc)` on `last_non_activity_message` so REST and cable both serialize the same most-recent preview * fix: address CodeRabbit round 8 feedback - ReactionsController#current_user_reaction: also match on content_attributes.in_reply_to_external_id = @target_message.source_id (via OR with the existing in_reply_to check), so WhatsApp-echoed reactions persisted by the incoming handlers — where in_reply_to could be blanked if the target wasn't resolvable at save time — are found and toggled instead of stacking a duplicate self-reaction - Mirror the same defensive OR check in the frontend MessagesView#findCurrentUserReaction, and thread the target's source_id through the toggleReaction event from Message.vue so the lookup sees it * fix: address CodeRabbit round 9 feedback - emoji_payload_valid?: tighten the final property check from \p{Emoji} to \p{Extended_Pictographic} so plain "1", "#", "*" (which Unicode tags as Emoji because they're valid keycap bases) are rejected as reaction payloads - EmojiReactionPicker: mirror the translated `title` into `aria-label` on the icon-only smile-plus / plus buttons so screen readers announce a meaningful action name - internalChat ReactionDisplay: close the popover when the post-removal state would leave ≤1 reactions, so a singleton-user popover never lingers after removing one of a pair - EventDataPresenter + conversation jbuilder: strip HTML before truncating `in_reply_to_snippet` so reactions to email/HTML bubbles don't surface literal "<p>..." markup in the chat-list preview * fix: address CodeRabbit round 10 feedback - MessageList#reactionsByMessageId: break createdAt ties with `<=` so a later iteration wins on second-resolution tie; two toggles in the same second no longer leave the chip pointing at a stale row - MessagePreview: require a non-empty `message.attachments` array (via `?.length`) before taking the attachment preview branch, so a removed reaction with `[]` no longer renders the attachment placeholder - MessagesView#findCurrentUserReaction: replace the sort-based pick with a reduce that deterministically takes the last element on tie, so a fast toggle can't hit a stale/deleted row with the same created_at - Baileys group handler: guard against `@sender_contact.blank?` before dispatching mark_existing_reaction_as_removed, otherwise a nil sender would fall into the senderless-outgoing branch and match the wrong row - WhatsApp reaction-removal lookups (Cloud, Baileys, Z-API): scope the base query to `inbox_id: inbox.id` so a colliding WhatsApp message id across inboxes can never mutate a reaction row from another inbox * fix: address CodeRabbit round 11 feedback - ReactionsController#emoji_payload_valid?: broaden the final property check to accept flag and keycap emoji. `\p{Extended_Pictographic}` by itself is per-codepoint, so 🇧🇷 (two Regional Indicators) and 1️⃣ (digit + VS16 + U+20E3) failed validation. Allow any grapheme cluster that contains at least one pictographic codepoint, a Regional Indicator, or the combining keycap, while still rejecting plain ASCII like "ok", "1", "#" - Message.vue#canShowReactionToolbar: hide the picker when the target has no provider source_id, mirroring the server guard in ReactionsController#target_unreactable_error instead of letting the click fall through to a 422 - MessageList#reactionsByMessageId: fall back to a sourceId → id lookup when a reaction only carries `inReplyToExternalId` (WhatsApp echo / phone-originated), so its chip still renders against the target bubble after reload - getLastMessage: merge the fresher store fields onto the API snapshot instead of replacing it, so jbuilder-only enrichments like `in_reply_to_snippet` survive the store refresh * fix(reactions): preserve API fields on card preview and expose a11y state on quick picker * fix(reactions): consistent originalId resolution, natural PT-BR snippet phrasing, accurate outgoing-echo spec * fix(reactions): reject requests missing emoji param and align zapi outgoing-echo spec fixture * fix(reactions): activity preview fallback, camelCase event listener, EN snippet quoting, fromMe group removals, REST chat-only preview * fix(reactions): reject non-string emoji, scope page reactions to window, exempt reactions from human_response, add cloud multi-device removal * test(message): isolate hide_removed_reactions deleted-branch from blank-content branch * fix(reactions): coerce in_reply_to_snippet to plain String strip_tags returns an ActiveSupport::SafeBuffer; truncate preserves the class. When this snippet flowed into ActionCableBroadcastJob via the CONVERSATION_UPDATED dispatch, Sidekiq's strict-args check rejected the non-native JSON type, raising synchronously through the dispatcher and turning the reactions controller response into a 500 even though the row had already persisted. The UI then surfaced the generic 'failed to update reaction' toast despite the chip rendering correctly. Wrap with String.new so the broadcast payload contains plain Strings. * fix(reactions): don't auto-scroll to bottom on reaction add ADD_MESSAGE emits SCROLL_TO_MESSAGE for every new push, which makes sense for regular outgoing messages (the user just hit send and wants to see it). Reactions render as chips on the parent bubble, so the auto-scroll yanked the agent away from whichever older message they were reacting to. Skip the emit when the incoming message is flagged as a reaction. * fix(reactions): skip scroll on conversation-only updates triggered by reactions The reactions controller dispatches CONVERSATION_UPDATED so the chat list preview can refresh in place. UPDATE_CONVERSATION mutation always emitted SCROLL_TO_MESSAGE for the open conversation, so every toggle yanked the viewport back to the bottom even after the previous fix in ADD_MESSAGE. When the refreshed preview row is itself a reaction the update is preview-only and the scroll is unwanted; for a regular incoming message the latest non-activity row is the message itself, which still triggers the scroll as before. * fix(reactions): anchor compact picker to button side instead of centering The compact picker was centered on the smile button, so half its width always extended toward the bubble side and overflowed past the chat edge on short messages. Anchor it to the button's outer side and nudge 4px toward the bubble so it lines up with the trigger. * test(reactions): regression coverage for safebuffer + scroll skip The previous CodeRabbit rounds shipped three bugs the existing specs didn't catch: a SafeBuffer return from `strip_tags` that 500'd the reactions controller via Sidekiq strict-args, and two SCROLL_TO_MESSAGE emits (one per mutation) that yanked the open conversation to the bottom on every emoji toggle. Lock all three behaviors. Also tighten the spec policy in AGENTS.md so new features default to having specs instead of skipping them. * test(baileys): align send_message_body helper with id:updated_at format The reactions PR switched chatwootMessageId to "<id>:<updated_at>" so toggle/replace cycles get a fresh idempotency key against baileys-api, but the shared spec helper still merged the bare integer id. 18 baileys provider specs were silently broken on CI as a result. * fix(reactions): skip set_contact for unknown reaction-removal webhooks Reaction-removal cloud webhooks were unconditionally creating a contact even when the sender was unknown and there was nothing to remove, because set_contact ran before the reaction_removal? short-circuit (needed earlier so blocked-contact reconciliation works). Add a sender-agnostic existence check on the inbox/in_reply_to scope and bail out before set_contact when no candidate row exists. Also realign two specs that were not updated when the chatwootMessageId format gained an `:updated_at` suffix and when zapi reaction-removal short-circuited instead of creating a Message. * test(conversation): include last_non_activity_message in push_data fixture Reactions PR added last_non_activity_message to the push_data payload but conversation_spec's exact-match expectation wasn't updated, so the sharded CI shard that landed on this file flipped red.	2026-04-30 21:09:12 -03:00
Gabriel Jablonski	e032fc7774	feat(whatsapp): convert inbox between WhatsApp providers (#268) ... * feat(whatsapp): allow converting inbox between WhatsApp providers Adds a Convert flow to switch a WhatsApp inbox between the four supported providers (default/360dialog, whatsapp_cloud, baileys, zapi) without losing conversations, agents, or history. - Channel::Whatsapp#convert_provider! runs inside a transaction: disconnects the old provider, clears provider_connection and message_templates, assigns the new provider/config, and triggers webhook setup plus template resync on the new service. - New POST /api/v1/accounts/:id/inboxes/:id/convert_provider endpoint guarded by InboxPolicy#convert_provider? (admin only). - UI adds a Convert button on the inbox Settings page with a type-to-confirm ConvertInboxModal that lists the effects before redirecting to a dedicated route reusing the WhatsApp provider wizard in convert mode (phone number locked, current provider hidden from the picker). * chore(whatsapp): polish convert UI colors and expand specs - Settings: use slate for the Convert trigger and ruby for the modal confirm to mirror the delete gate instead of the less conventional amber variant. - Drop the redundant "current provider is hidden from the list" sentence from the convert wizard description. - Add specs for the post-conversion webhook setup path (triggered and skipped branches) and the sync_templates error-rescue behaviour. * fix: address CodeRabbit review on convert-provider flow - Whitelist provider_config keys in the convert endpoint via permit rather than permit!, and default to an empty hash when omitted so the request no longer crashes. - Pre-validate the new provider config before disconnecting the old session so a bad target config no longer terminates the existing provider; also keep the disconnect bound to the old provider_url. - Guard ConvertInboxModal's submit handler so pressing Enter cannot bypass the type-to-confirm gate, and migrate it to <script setup>. - Reject invalid ?provider= query values in convert mode so hidden providers (Twilio, the current provider) cannot be reached via URL. - Await the inbox fetch in InboxConvert before running the route guard so directly opening the route for a non-WhatsApp inbox redirects. - Remove the unreachable second CloudWhatsapp branch in Whatsapp.vue. * fix: address second CodeRabbit round on convert-provider flow - Unify provider picker validation so create mode also rejects unknown ?provider= values, with a single helper that accepts available providers plus the whatsapp_manual fallback. - Simplify the pre-validation rollback in convert_provider!: the errors snapshot/merge dance was redundant because assign_attributes does not clear errors. - Follow the repo convention of asserting on error.class.name so the rollback spec stays stable under reloading/parallel environments. - Strengthen the controller success spec with provider_connection and message_templates cleanup invariants, and set Content-Type on the templates stub so HTTParty parses the empty data array correctly. * fix: address third CodeRabbit round on convert-provider flow - Add 360Dialog entry to the Whatsapp provider catalog, keep it hidden from the create picker (preserving the existing fork behavior) but expose it in the convert picker where it is a valid target. Restore URL reachability for ?provider=360dialog in create mode. - Scope the WHATSAPP_MANUAL allowance to create mode only: the manual fallback flow is not reachable in convert mode. - Redirect to the inboxes list in InboxConvert when the inbox is still absent after the store fetch, so the page no longer stays blank. - Use an explicit allowlist of WhatsApp providers to gate the Convert button instead of negating Twilio, so adding a new WhatsApp channel type will not silently expose the flow. - Bind the disabled provider display field with :value instead of v-model, since the underlying computed is getter-only. - Add Content-Type: application/json to the templates stub in the model spec so HTTParty parses the empty data array. * fix: address fourth CodeRabbit round on convert-provider flow - Reject no-op conversions that target the same provider as the one already configured, so the endpoint no longer wipes provider connection and message templates on a request that changes nothing. - Call the provider service's disconnect directly so failures abort the conversion instead of being silently swallowed; otherwise the old external session could remain live while the inbox flips to the new provider. - Cover both behaviors with specs. * fix: address fifth CodeRabbit round on convert-provider flow - Reset the Vuelidate state when closing ConvertInboxModal so reopening the gate does not surface stale validation errors. - Call teardown_webhooks before converting away from whatsapp_cloud so the Meta webhook subscription is removed for embedded_signup channels, mirroring the destroy-time cleanup (manual-setup channels keep the existing no-op behavior). Swallow teardown failures so a flaky Meta call does not abort the swap. - Switch the rollback specs to compare message_templates counts instead of the boolean be_present matcher so they remain meaningful if the fixture happens to have an empty templates list. * fix: address sixth CodeRabbit round on convert-provider flow - Derive the convert header's current-provider label from the shared PROVIDER_CATALOG so the picker and header stay in sync. - Assert the full Cloud provider_config payload and the absence of the Baileys-only provider_url key on both the controller success spec and the model atomic-swap spec. - In the sync-error spec, reload and assert that the record was actually flipped to the new provider before the sync rescue fires, so the test can't pass on a pre-save failure. * test: pin 422 error payload on convert_provider negative paths The unsupported-conversion and invalid-config specs only checked the status code, so they would have stayed green if the 422 started coming from a different branch. Pin the response body so each example actually covers the failure case it names. * fix(baileys): save custom host as provider_url, not url The Baileys form was writing the custom endpoint to provider_config['url'] while the backend reads provider_config['provider_url']. That silently broke the custom-host feature for newly created or converted Baileys inboxes: they always fell back to BAILEYS_PROVIDER_DEFAULT_URL. Align the key on both ends. * fix(whatsapp): skip second validation pass in convert_provider! The transaction's save! was re-running validate_provider_config after the old provider's session had already been disconnected, so a transient Graph API failure on the second check could roll back the swap while leaving the external session terminated — the exact inconsistency the pre-flight valid? was meant to rule out. Capture the validated provider_config snapshot after valid? (so fields populated by before_validation callbacks like webhook_verify_token are preserved) and switch the final persist to save!(validate: false) so the earlier check stays authoritative. * fix: normalize provider-conversion failures and pass accountId - The convert_provider action only rescued ActiveRecord::RecordInvalid, so disconnect/teardown failures bubbled up as 500 with no stable payload. Catch StandardError, log the class + message, and return a 422 with a generic user-facing message so the dashboard can surface the error consistently. - Nested settings routes live under /accounts/:accountId, so the router push from Settings.vue must include accountId alongside inboxId. Mirrors how sibling pages navigate to settings_inbox_show. * fix: report missing :provider as 400 and sync modal v-model - The generic rescue StandardError on convert_provider was masking ActionController::ParameterMissing behind a misleading provider-conversion error message. Catch it explicitly before the generic rescue and return 400 with the parameter-missing message. - ConvertInboxModal's closeModal now drives localShow to false so parents using v-model:show stay in sync on every close path, not only when the explicit onClose listener flips the flag. * fix(whatsapp): serialize concurrent convert_provider calls with_lock Without a per-record lock, two admin requests against the same inbox could both pass the pre-flight validation, race the disconnect/save, and then run setup_webhooks/sync_templates in arbitrary order, leaving the persisted provider out of sync with the external configuration. Wrap the whole convert flow in with_lock so the loser blocks until the winner commits; the subsequent no-op guard then rejects a second conversion request targeting the provider the first one just set. * test: harden convert_provider policy + controller failure specs - Pass accountId explicitly in InboxConvert redirects so the route navigation mirrors how Settings.vue reaches settings_inbox_convert. - Add a spec that assigns the agent to the inbox and still expects 401, so a future regression in InboxPolicy#convert_provider? can no longer slip past on the show policy alone. - Add a spec that stubs convert_provider! to raise StandardError and asserts the controller's generic-failure 422 payload, pinning the dashboard contract for provider-side failures. * test: pin convert_provider success response payload Parse the rendered body and assert provider + provider_config so the spec catches regressions where the DB is updated correctly but the serialized response drifts (dashboard store commits response.data). * fix(whatsapp): reset teardown guard after pre-conversion webhook cleanup teardown_webhooks memoizes @webhook_teardown_initiated = true to prevent double execution during destroy. Calling it from convert_provider! leaves that flag set, so a subsequent destroy! or follow-up conversion on the same instance would skip webhook removal silently. Reset the flag in an ensure block so the destroy-time guard stays scoped to destroy only. * fix: include accountId in post-conversion redirect params * test: pin same-provider convert returns 422 * fix(whatsapp): reset template columns when post-conversion sync fails * fix(convert): enforce provider allowlist in InboxConvert route guard * test: broaden Cloud templates stub to match account-scoped path * test(whatsapp): cover cloud to baileys conversion branch	2026-04-18 20:57:27 -03:00
Gabriel Jablonski	a996b920e8	feat: group conversations (#228) ... * feat: add group and conversation types to contacts and conversations, and implement conversation group membership model * chore: add factory and specs for conversation group member model * chore: add group type checks and associations for contacts and conversations * refactor: remove scopes from ConversationGroupMember model * refactor: remove scopes from ConversationGroupMember model specs * refactor: enhance conversation type migration with concurrent indexing * feat: add is_active index and scopes to ConversationGroupMember model * feat: implement GroupConversationHandler for managing group conversations * feat: add group_type attribute to contact creation * fix: update WHATSAPP_CHANNEL_REGEX to allow up to 20 digits to handle group jid * feat: handle group JID format in remote_jid method * chore: update group contact info when finding or creating group contact * chore: refactor and implement contact message handling and message creation logic for baileys single contact conversation * feat: implement group message handling and metadata fetching in WhatsApp service * chore: add spec for group type handling in contact creation for individual and group contacts * chore: add specs for test scopes in conversation group members * chore: update documentation for sender phone extraction in group conversation handler * chore: move GroupConversationHandler concern to correct dir * chore: implement specs for recipient_id handling to individual and group contacts * chore: add group message handling specs for incoming messages * chore: enhance group message handling to prevent race conditions * chore: add group_metadata method to with error handling * chore: add test for sending messages to group recipients in WhatsappBaileysService * chore: raise error for unsuccessful response in group_metadata method * chore: adds tests for group metadata retrieval and error handling * chore: refactor build_sender_contact_attributes to avoid double call methods * chore: update error handling for attachment download failure in message creation * chore: optimize update_contact_info method to use compact hash for updates * chore: simplify find_or_create_sender_contact method return values * chore: rename group and individual contact message handlers * chore: remove pointless comments from group contact message handler methods * chore: refine sender JID extraction logic to remove unnecessary checks * chore: remove phone number in spec for group contact attributes * chore: implement sync_group route * chore: implement get group_members route * fix: sync_group participants creation handling * chore: update contact avatar handling in group message processing * chore: move sync_group functionality for conversation model * feat: add sync_group action to ConversationsController and route * fix: set contact name to phone in group message processing * chore: refine group member retrieval logic in sync_group service and view * feat: implement group participants update handling * feat: implement group updates handling and localization for group activities * chore: add handling for group membership requests and icon changes * chore: add authorization for sync_group action in ContactsController * chore: add sync_group endpoint specs for contact management * chore: add authorization for sync_group action in ConversationsController * chore: add specs for sync_group endpoint in ConversationsController * chore: refactor index action in GroupMembersController for improved conversation filtering * chore: add request specs for group_members endpoint in ContactsController * chore: add specs for sync_group method in Conversation model * chore: add specs for sync_group method in Channel::Whatsapp model * chore: remove comments in find_or_create_group_conversation method * chore: add specs for Contacts::SyncGroupService to validate group contact behavior * chore: add specs for Whatsapp::BaileysHandlers::GroupsUpdate to validate group updates * chore: add specs for Whatsapp::BaileysHandlers::GroupParticipantsUpdate to handle group participant actions * chore: add fallback for identifier when contact has no phone_number in SendOnWhatsappService * chore: add specs for group membership request and icon change handling in MessagesUpsert * chore: add specs for sync_group method to handle group metadata and participant updates * chore: update sync_group method to retrieve group members and adjust JSON response * chore: update conversation query to filter by group type in GroupMembersController * chore: update conversation creation in group_members_controller_spec to specify conversation_type as group * chore: update find_or_create_group_conversation to include pending conversations * chore: refactor sync_group method and enhance specs for group conversation handling * feat: add GroupEventHelper module for managing group activities and contacts * chore: refactor group contact inbox and conversation creation methods in group handlers * chore: remove unnecessary check for blank participant contacts in sync_group_members method * feat: implement message receipt update handling for WhatsApp integration * chore: resolve rubocop rule for update_last_seen_at method * chore: update swagger with endpoints for syncing group information and listing group members * chore: integrate Contacts::SyncGroupService in group members controller, enhance error handling and update swagger * chore: include participant information in reaction and quoted message keys for send message in group conversations * chore: enhance whatsapp_baileys_service with participant handling for message keys * feat: add skill for writing RSpec tests in the project * fix: update recipient_id logic to directly use contact identifier for group contacts * chore: implement group stub message handling for membership requests and icon changes * fix: update whatsapp inbox source_id validation regex spec * chore: fix spec for contact syncing group * chore: remove readTimestamp handling and related tests for message read updates in group * Cayo oliveira/cu 86af01932/4 backend gerenciamento dos grupos (#221) * feat: add is_active index and scopes to ConversationGroupMember model * feat: implement GroupConversationHandler for managing group conversations * feat: add group_type attribute to contact creation * fix: update WHATSAPP_CHANNEL_REGEX to allow up to 20 digits to handle group jid * feat: handle group JID format in remote_jid method * chore: update group contact info when finding or creating group contact * chore: refactor and implement contact message handling and message creation logic for baileys single contact conversation * feat: implement group message handling and metadata fetching in WhatsApp service * chore: add spec for group type handling in contact creation for individual and group contacts * chore: add specs for test scopes in conversation group members * chore: update documentation for sender phone extraction in group conversation handler * chore: move GroupConversationHandler concern to correct dir * chore: implement specs for recipient_id handling to individual and group contacts * chore: add group message handling specs for incoming messages * chore: enhance group message handling to prevent race conditions * chore: add group_metadata method to with error handling * chore: add test for sending messages to group recipients in WhatsappBaileysService * chore: raise error for unsuccessful response in group_metadata method * chore: adds tests for group metadata retrieval and error handling * chore: refactor build_sender_contact_attributes to avoid double call methods * chore: update error handling for attachment download failure in message creation * chore: optimize update_contact_info method to use compact hash for updates * chore: simplify find_or_create_sender_contact method return values * chore: rename group and individual contact message handlers * chore: remove pointless comments from group contact message handler methods * chore: refine sender JID extraction logic to remove unnecessary checks * chore: remove phone number in spec for group contact attributes * chore: implement sync_group route * chore: implement get group_members route * fix: sync_group participants creation handling * chore: update contact avatar handling in group message processing * chore: move sync_group functionality for conversation model * feat: add sync_group action to ConversationsController and route * fix: set contact name to phone in group message processing * chore: refine group member retrieval logic in sync_group service and view * feat: implement group participants update handling * feat: implement group updates handling and localization for group activities * chore: add handling for group membership requests and icon changes * chore: add authorization for sync_group action in ContactsController * chore: add sync_group endpoint specs for contact management * chore: add authorization for sync_group action in ConversationsController * chore: add specs for sync_group endpoint in ConversationsController * chore: refactor index action in GroupMembersController for improved conversation filtering * chore: add request specs for group_members endpoint in ContactsController * chore: add specs for sync_group method in Conversation model * chore: add specs for sync_group method in Channel::Whatsapp model * chore: remove comments in find_or_create_group_conversation method * chore: add specs for Contacts::SyncGroupService to validate group contact behavior * chore: add specs for Whatsapp::BaileysHandlers::GroupsUpdate to validate group updates * chore: add specs for Whatsapp::BaileysHandlers::GroupParticipantsUpdate to handle group participant actions * chore: add fallback for identifier when contact has no phone_number in SendOnWhatsappService * chore: add specs for group membership request and icon change handling in MessagesUpsert * chore: add specs for sync_group method to handle group metadata and participant updates * chore: update sync_group method to retrieve group members and adjust JSON response * chore: update conversation query to filter by group type in GroupMembersController * chore: update conversation creation in group_members_controller_spec to specify conversation_type as group * chore: update find_or_create_group_conversation to include pending conversations * chore: refactor sync_group method and enhance specs for group conversation handling * feat: add GroupEventHelper module for managing group activities and contacts * chore: refactor group contact inbox and conversation creation methods in group handlers * chore: remove unnecessary check for blank participant contacts in sync_group_members method * chore: update swagger with endpoints for syncing group information and listing group members * chore: integrate Contacts::SyncGroupService in group members controller, enhance error handling and update swagger * fix: update recipient_id logic to directly use contact identifier for group contacts * chore: implement group stub message handling for membership requests and icon changes * fix: update whatsapp inbox source_id validation regex spec * chore: fix spec for contact syncing group * fix: optimize update_last_seen_at method to use update_columns * feat: Implement full frontend and backend support for group conversations - Added PRD for group conversations detailing frontend and backend requirements. - Created new Baileys TypeScript definitions for group-related functions. - Renamed `conversation_type` to `group_type` in the database and updated all references. - Implemented API serialization for `group_type` in conversation and contact responses. - Developed Vuex store module for managing group members. - Created UI components for group management, including group creation, member management, and metadata editing. - Integrated @mention functionality for group conversations and real-time updates via ActionCable. * feat: [US-001] - Rename conversation_type to group_type on conversations - Add migration to rename column and indexes - Update Conversation model enum to group_type - Update GroupConversationHandler concern - Update controllers (contacts, group_members) - Update all backend specs * chore: mark US-001 complete, update progress log, fix rubocop annotation * feat: [US-002] - Serialize group_type fields in API responses * feat: [US-003] - Add group_type filter to conversations index * feat: [US-004] - Add group_type to filter_keys.yml and FilterService * feat: US-005 - Backend group creation endpoint - Add POST /api/v1/accounts/:account_id/groups endpoint - Add Groups::CreateService to orchestrate Baileys group creation - Extend WhatsappBaileysService and BaseService with group management methods - Add routes for group members, metadata, invite, and join requests - Returns 403 when agent lacks inbox access, 422 when provider is unavailable * feat: US-006 - Backend add/remove members and role management endpoints - Add create/destroy/update actions to GroupMembersController - Delegate group management methods from Channel::Whatsapp to provider_service - create adds members via Baileys and creates ConversationGroupMember records - destroy removes a member by ID and sets is_active false - update promotes/demotes a member and updates their role * feat: US-007 - Backend group metadata update endpoint - Add PATCH /contacts/:id/group_metadata endpoint - Updates group subject via Baileys and syncs contact name - Updates group description via Baileys and syncs additional_attributes.description - Returns 422 when provider is unavailable * feat: US-008 - Backend invite link management endpoints - Add GET /contacts/:id/group_invite to retrieve current invite code/url - Add POST /contacts/:id/group_invite/revoke to revoke and get new invite code/url - Returns 422 when provider is unavailable * feat: US-009 - Backend join request management endpoints - Add GET /contacts/:id/group_join_requests to list pending join requests - Add POST /contacts/:id/group_join_requests/handle to approve/reject requests - Uses request_action param to avoid conflict with Rails reserved params[:action] - Returns 422 when provider is unavailable * feat: US-010 - Extend MentionService for contact mentions - Extract mention://contact/ID/Name URIs from message content - Store mentioned contact IDs in message.content_attributes[mentioned_contacts] - Existing user/team mention handling unchanged * feat: US-011 - Frontend API clients for all group endpoints - Add app/javascript/dashboard/api/groupMembers.js - Exports 11 methods: getGroupMembers, syncGroup, createGroup, updateGroupMetadata, addMembers, removeMembers, updateMemberRole, getInviteLink, revokeInviteLink, getPendingRequests, handleJoinRequest * feat: US-012 - Frontend Vuex store module groupMembers - Add groupMembers store module with fetch, sync, addMembers, removeMembers, updateMemberRole actions - Add SET_GROUP_MEMBERS and SET_GROUP_MEMBERS_UI_FLAG mutation types - Register module in store index * feat: US-013 - Frontend i18n keys for group features - Add groups.json with keys for group info, filter, creation modal, metadata editing, invite link, member management, join requests, and mention dropdown - Register groups.json in i18n locale en/index.js Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * feat: US-014 - Frontend group_type filter in ConversationBasicFilter - Add chatGroupTypeFilter state, getter, mutation, and action to conversations store - Add getChatGroupTypeFilter getter - Add group_type param to ConversationApi.get() - Add Type filter section to ConversationBasicFilter with All/Individual/Group options - Persist group_type to UI settings under conversations_filter_by.group_type - Restore group_type from UI settings on page load - Include groupType in conversationFilters and pass as group_type param to API Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * feat: US-013 - Frontend — i18n keys for group features (en + pt-BR) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: [US-014] - Frontend — add group_type filter to ConversationBasicFilter All implementation was already in place from prior work: - ConversationBasicFilter.vue has Type section with All/Individual/Group options - ChatList.vue handles group_type in conversationFilters and restores from UI settings - Store has setChatGroupTypeFilter action, getChatGroupTypeFilter getter - API maps groupType → group_type query param Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-015 - Frontend — add group_type to advanced filter system - Add GROUP_TYPE to CONVERSATION_ATTRIBUTES in filterHelper.js - Add group_type filter definition in provider.js (components-next) - Add group_type to legacy advancedFilterItems/index.js and filterAttributeGroups - Add group_type to automationHelper conditionFilterMaps - Add group_type to customViewsHelper getValuesForFilter - Add group_type options to ChatList setParamsForEditFolderModal - Add GROUP_TYPE i18n key in en and pt_BR advancedFilters.json Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-016 - Frontend — GroupContactInfo basic display Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-017 - Frontend — GroupContactInfo sync button Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-018 - integrate GroupContactInfo in ContactPanel - Import GroupContactInfo component - Conditionally render GroupContactInfo when group_type === 'group' - Keep ContactInfo for individual conversations (no regression) - Dynamic sidebar title: 'Group' for groups, 'Contact' for individual - contact_notes and contact_attributes accordion sections unchanged Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-019 - Frontend — group creation UI modal Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-020 - Frontend — member management UI in GroupContactInfo Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-021 - Frontend — group metadata editing UI Add inline editing for group name, description, and avatar in GroupContactInfo: - Click group name to edit inline, save on Enter/blur - Click description to edit inline with textarea, save on blur - Click avatar to open file picker for upload via contacts/update - Loading states on all fields during save - Success/error alerts for all operations - updateGroupMetadata action added to groupMembers store Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-022 - Frontend — invite link management UI Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-023 - Frontend — join request management UI Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-024 - Frontend — group message bubbles: sender name with color - Add sender name display above incoming message bubbles in group conversations - Deterministic color per sender using AVATAR_COLORS palette (name.length % 6) - Sender name hidden for consecutive messages from the same sender - Individual conversation bubbles unchanged - Pass groupWithPrevious and isGroupConversation props through MessageList → Message Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-025 - Frontend — group message bubbles: sender avatar Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: Add Ralph Wiggum AI agent script for managing tool execution and progress tracking * feat: US-026 - Frontend — @mention dropdown for group conversations - Create TagGroupMembers.vue component for group member mention suggestions - Modify Editor.vue: add isGroupConversation/groupContactId props, render TagGroupMembers for group non-private context - Modify ReplyBox.vue: compute isGroupConversation and groupContactId from currentChat, pass to WootMessageEditor - @ mention plugin isAllowed now triggers for group conversations - In individual conversations or private notes, existing behavior unchanged Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-027 - Frontend — mention rendering in group message bubbles Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-028 - Frontend ActionCable handler for contact.group_synced event - Backend: Include group_members data in contact.group_synced ActionCable payload - Frontend: Register contact.group_synced handler in ActionCableConnector - Frontend: Add setGroupMembers action to groupMembers store for direct commits - Tests: ActionCable handler spec + groupMembers store spec for new action Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: Update progress tracking for group conversations feature - mark tests as passing * fix: sender click case mismatch and filter dropdown spacing - Message.vue: use case-insensitive comparison for sender type check (Contact.push_event_data returns 'contact' but SENDER_TYPES.CONTACT is 'Contact') - ConversationBasicFilter.vue: replace last:mt-4 with flex-col gap-4 for consistent spacing between all three filter sections * fix: four bugs found during manual testing review - ContactPanel.vue: fix i18n key GROUP.INFO.SIDEBAR_TITLE → GROUP.SIDEBAR_TITLE - groupMembers.js API: fix syncGroup HTTP method GET → POST to match backend route - group_members_controller.rb: remove SyncGroupService from index action - filterHelpers.js: add missing group_type case to getValueFromConversation * docs: update progress with bug fix learnings * chore: implement group creation functionality in UI components * chore: add copy invite link functionality and update UI components * feat: US-041 - Backend — ensure group_type is set on existing contacts and conversations GroupConversationHandler#update_group_contact_info now sets group_type: :group on contacts that are incorrectly typed as individual. GroupConversationHandler#find_or_create_group_conversation updates existing conversation's group_type to :group if it is currently :individual. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * chore: mark US-041 as complete Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-029 - i18n keys for You badge and group settings (en + pt-BR) All i18n keys already existed from prior iterations. Verified presence and updated PRD status. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-030 - fix Baileys API route/method mismatches Fix on_whatsapp to dig('data') before accessing first element. Update spec stubs to match { data: [...] } response envelope. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-031 - group_leave, group_setting_update, group_join_approval_mode methods All methods, delegates, and error handling already implemented. Verified specs pass. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-032 - persist group settings, invite code, and profile picture during sync Add try_update_group_avatar to fetch and attach group profile picture during sync_group. Update spec stubs for profile-picture-url endpoint. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-033 - GroupSettingsController with leave, update, toggle Controller and routes already implemented. Verified rubocop passes. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-034 - remove inbox_contact_id from provider_config and jbuilder Already removed in prior iterations. Verified no references remain. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-035 - refactor TagGroupMembers to phone_number matching Already implemented. Verified excludePhoneNumber prop and filtering. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-036 - remove InboxContact.vue and settings tab Already removed in prior iterations. Verified no references remain. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-037 - add You badge in GroupContactInfo member list Already implemented with isOwnMember check and blue badge styling. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-038 - fix inline edit for group name and description Already implemented with phone number normalization. Verified code. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-039 - group settings section UI with toggles Already implemented. Settings toggles, API calls, and i18n verified. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-040 - leave group UI with confirmation and auto-resolve Already implemented. Leave button, confirmation, and API call verified. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-050 - Create GroupMember model and migration New group_members table with group_contact_id, contact_id, role, is_active. Unique index on (group_contact_id, contact_id). Associations added to Contact. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-064 - Helper method to find channel from group contact Add Contact#group_channel to decouple channel lookup from conversations. Update GroupMembersController and GroupSettingsController to use it. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-052 - Update GroupConversationHandler to use GroupMember Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-057 - Update GroupMembersController to query GroupMember Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-058 - Update GroupSettingsController to not depend on conversations Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-060 - Update group_members jbuilder views Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-059 - Remove group_members association from Conversation model Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat: US-051 - Remove ConversationGroupMember model and table Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * chore: mark all stories complete, update progress Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * feat(groups): real-time group panel, avatar refresh on icon change, editable name/description - Add group_type to Conversations::EventDataPresenter#push_data and Contact#push_event_data so WebSocket events carry the field, enabling the frontend to switch to GroupContactInfo in real-time - Update handle_icon_change_stub to call try_update_group_avatar with force: true, purging the cached avatar and fetching the new one - Add force parameter to try_update_group_avatar to support re-fetching - Remove isInboxAdmin gate from name/description editing in GroupContactInfo so any user can click to edit (server validates) * fix(groups): rewrite SyncGroupService and simplify group metadata channel lookup - Rewrite SyncGroupService to use contact.group_channel directly instead of iterating conversations; find or create a conversation for sync - Simplify GroupMetadataController to use @contact.group_channel instead of querying conversations; remove local contact/attribute updates since the Baileys API handles persistence via webhook events * feat(groups): resolve conversations when inbox phone leaves or is removed - Add resolve_conversations_if_inbox_left to GroupParticipantsUpdate - Resolves all open/pending conversations when the inbox phone number is removed from or leaves a group * feat(groups): add paginated member list with infinite scroll - Backend: add pagination to GroupMembersController (page/per_page, default 10, ordered admins first); add meta with pagination info to the jbuilder response - Frontend: update groupMembers API to accept page param; add APPEND_GROUP_MEMBERS and SET_GROUP_MEMBERS_META mutations; implement paginated fetch with append and isFetchingMore flag in store * feat(groups): support Ctrl+Click on group message sender to open in new tab - navigateToGroupSender now accepts the event and checks for Ctrl/Cmd+Click to open the sender contact in a new tab * chore(i18n): update leave group confirmation text in en and pt_BR * fix(groups): handle phone format differences in You badge and admin detection - Extract phonesMatch helper that compares last 8 digits as fallback, handling Brazilian 9th digit discrepancy (e.g. +5587988465072 vs +558788465072) - Apply to both isOwnMember and isInboxAdmin computed properties * feat(groups): auto-sync members on mount, show existing members immediately - On mount, fetch existing DB members first so they display instantly - Then silently attempt a background sync to refresh from WhatsApp - If sync fails (e.g. WhatsApp disconnected), existing members remain displayed without any user-facing error * fix(groups): pin own member on first page and return inbox phone in meta The "You" badge was not appearing because the inbox's own member could be missing from the first paginated page in large groups (admins sorted first). Backend: - Pin the inbox's own member at the top of page 1 regardless of sort order - Return inbox_phone_number in the group members meta response - Use last-8-digit SQL fallback for Brazilian 9th-digit phone mismatches Frontend: - Use meta.inbox_phone_number for the inboxPhone computed - Fix declaration order to satisfy no-use-before-define lint rule * fix(groups): fix member action dropdown clipped by overflow container The promote/demote/remove dropdown menu was invisible because the member list had `overflow-y-auto max-h-80`, clipping any absolutely-positioned dropdown rendered inside it. - Remove overflow container from member list; let the sidebar scroll - Replace scroll-based infinite loading with IntersectionObserver on a sentinel element for cleaner pagination trigger - All member action logic (promote, demote, remove) was already wired; the dropdown is now visible on hover * fix(groups): keep member action dropdown visible when menu is open The opacity-0/group-hover classes on the action menu wrapper caused the DropdownMenu to become invisible as soon as the mouse left the row. Now the wrapper stays fully opaque while the menu is active. * fix(groups): move clickaway to member list wrapper to prevent instant close v-on-clickaway was bound to every member's action div individually. Clicking the three-dot button on one member fired closeMemberMenu from all other members' clickaway handlers, closing the menu instantly. Moved the directive to the single member list container instead. * feat: add WhatsApp mention conversion (incoming + outgoing) - New MentionConverterService for bidirectional mention handling - Incoming: converts @phone/mentionedJid to mention://contact/ URIs - Outgoing: extracts mention://contact/ URIs into WhatsApp mentions array - Supports @everyone/todos group mentions - WhatsApp renderer preserves mention display text instead of raw URI * fix: preserve mention display text in WhatsApp renderer mention:// URIs now render as display name text instead of the raw URL when converting markdown to WhatsApp format * feat: add @everyone mention option in group conversations - Everyone item shown at top of mention dropdown - Searchable by 'all', 'todos', 'everyone' keywords - i18n keys added for en and pt-BR * refactor: use Switch component for group settings toggles - Add disabled prop to Switch component - Replace custom toggle buttons in GroupContactInfo with Switch - Loading spinner shown alongside toggle while toggling * feat(whatsapp): add group sync status tracking (group_left, group_last_synced_at) * feat(whatsapp): hide group management UI when group_left is true * fix(groupMembers): include inbox phone number in group members state and sync event * feat(whatsapp): wrap group settings and leave in Accordion component * feat(groupMembers): handle group creator modification errors and update error messages * feat(groupMembers): enhance invite link functionality and clean up UI state after copying * refactor: remove sync_group functionality from conversations and related specs * feat(GroupContactInfo): implement scroll-based loading for group members * docs(swagger): add group API endpoints and remove conversation sync_group - Remove dead conversation/{id}/sync_group swagger entry and file - Update group_members.yml with pagination params, POST operation, and $ref schema - Add swagger for: group_members_member (PATCH/DELETE), group_metadata, group_invite, group_invite_revoke, group_join_requests, group_join_requests_handle, group_settings, group_settings_leave, group_settings_toggle_join_approval, groups/create - Add group_member schema definition - Add Groups tag to application tag_groups - Register all 12 group endpoints in paths/index.yml * feat(WhatsappBaileysService): enhance mention handling by replacing @DisplayName with @lid/@phone in outgoing text * feat(groups): move group sync to background job with 15-min cooldown - Create Contacts::SyncGroupJob that checks group_last_synced_at before calling SyncGroupService (skips if < 15 min) - Controller sync_group now enqueues the job and returns 202 Accepted - Delete sync_group.json.jbuilder (no longer needed) - Frontend sync action is fire-and-forget; results via ActionCable - Auto-trigger sync on conversation select and panel mount - Remove manual sync button from GroupContactInfo * fix: show group members list even after leaving group\n\nKeep the members section visible in read-only mode when\ngroup_left is true. Admin actions (add member, promote,\ndemote, remove) remain hidden. Pending Join Requests and\nAdvanced Options also stay hidden. * fix: disable group name/description/avatar editing when group_left is true * fix: remove @all mention and fix Enter key in group mention dropdown\n\n- Remove the @all/everyone special mention from TagGroupMembers since\n no channel provider currently supports mentioning all participants\n- Fix Enter key sending message instead of inserting selected mention\n in group conversations. The root cause was Editor.vue only emitting\n toggleUserMention=true for private notes (isPrivate), leaving\n ReplyBox unaware the group mention dropdown was open. Now also\n emits for isGroupConversation.\n- Add TagGroupMembers spec covering filtering, exclusion, and emission" * fix: address PR review feedback for group conversations - Fix nil safety in group_invites and group_join_requests controllers by replacing group_conversation.inbox.channel with @contact.group_channel - Add before_action guard in group_members_controller to validate contact is a group with identifier before create/update/destroy - Persist metadata locally in group_metadata_controller after provider calls (subject -> name, description -> additional_attributes) - Add server-side allow_group_creation? check in groups_controller - Add word boundary to mention regex to prevent matching inside words - Remove useless catch clauses in groupMembers store (try/finally only) - Default groupType to [] in customViewsHelper to prevent crash - Fix swagger parameter name mismatch (contact_id -> id) across all group endpoint YML files for consistency * fix: address PR #228 review feedback - strong params, guards, and safety fixes * fix: dispatch real-time events for Baileys group participant and metadata updates Both group-participants.update and groups.update handlers were updating backend data (GroupMember records, Contact attributes) but never dispatching ActionCable events, leaving the frontend member list and group metadata stale until manual sync. Changes: - Add dispatch_group_synced_event helper to GroupEventHelper concern - Dispatch CONTACT_GROUP_SYNCED after participant add/remove/promote/demote - Dispatch CONTACT_GROUP_SYNCED after group subject/description/settings changes - Frontend: onContactGroupSynced also dispatches contacts/updateContact to refresh group name, description and settings in the sidebar * fix: enhance member menu positioning and close behavior on sidebar scroll * feat: implement group property updates and enhance toast notifications * fix: update WhatsApp channel regex to allow optional hyphenated numbers * feat: implement group admin functionalities including leave, update properties, and toggle join approval * refactor: simplify group message handling by removing metadata fetching and syncing methods * chore: remove raph files * feat: update Portuguese translations for 'Read More' and 'Insert Read More' phrases * feat: enhance group admin functionalities with join approval and member add modes * feat: enhance group join request handling by adding removal of handled requests and updating pending join requests * feat: restrict message sending in announcement mode groups When a Baileys WhatsApp group has announcement mode enabled (announce=true), only admin members can send messages. This adds: - Frontend: disabled editor + banner for non-admin inbox in announcement groups - Backend: validation in SendOnWhatsappService to reject messages - Shared phone helper utility extracted from GroupContactInfo - i18n keys for en and pt_BR * feat: add group sync job enqueueing and improve avatar update handling * feat: add functionality to reset invite link and confirm member addition restrictions * feat: update group name extraction logic to handle nil values * feat: add inbox admin status handling and update related components * feat: remove group conversation resolution on leave action * feat: enhance group sender avatar interaction with tooltip and cursor pointer * feat: add force option to SyncGroupJob and update related specs * feat: enhance invite link handling and avatar update logic in group conversations * chore: remove prd.json * fix: change group sender name display from block to inline-block for better layout * feat: add group members loading check and fetch logic in MessagesView and ReplyBox components * feat: allow id and firstUnreadId props to accept both Number and String types feat: add vOnClickOutside import to Editor component feat: enhance Portuguese translations for integrations and settings fix: change button color in GroupContactInfo component from green to teal * feat: soft-disabled group conversations with activity tracking Groups start in a soft-disabled state by default when using Baileys. Chatwoot still creates group conversations but does not process every incoming message. Instead, Baileys accumulates group messages and sends periodic groups.activity webhook events to update last_activity_at. Backend: - Add WHATSAPP_GROUPS_ENABLED env var and groups_enabled? class method - Send groupsEnabled in Baileys connection setup - Create groups.activity handler to update conversation last_activity_at - Gate group message processing behind groups_enabled? check - Expose groups_enabled via inbox API Frontend: - Add warning banner with CTA to app.fazer.ai on disabled group conversations - Disable reply editor for non-private-note mode when groups disabled - Add i18n strings for en and pt_BR Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: use method for groups disabled banner action to avoid window scope issue Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: broadcast conversation update after groups.activity event update_columns bypasses ActiveRecord callbacks, so the ActionCable broadcast was never triggered when last_activity_at changed. Dispatch a CONVERSATION_UPDATED event explicitly so the sidebar updates in real-time. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * feat: show unread dot for soft-disabled group conversations with activity Since soft-disabled groups don't create messages, unread_count is always 0 and the standard badge won't show. Detect unread state by comparing last_activity_at > agent_last_seen_at for these groups and display a teal dot indicator instead of a count badge. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: clear unread dot when agent opens soft-disabled group conversation The update_last_seen endpoint skipped updating agent_last_seen_at when there were no unread messages (the throttle path). For soft-disabled groups that never create messages, this meant the dot indicator could never be cleared. Add an unseen_activity? check that bypasses the throttle when last_activity_at > agent_last_seen_at. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * feat: group avatar upload to provider and fix icon change sync - Route avatar upload through GroupMetadataController to push to WhatsApp provider before saving locally - Add update_group_picture to baileys service and base service - Fix buildContactFormData crash when social_profiles is undefined - Make try_update_group_avatar public so GROUP_CHANGE_ICON stub handler can call it from outside the service class Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: update specs for group conversations feature changes - Add groupsEnabled param to setup_channel_provider and handle_channel_error WebMock stubs - Add group-request-participants-list stub for sync_group tests - Add group_type to push_event_data expected hash - Set last_activity_at in throttle tests to prevent unseen_activity? bypass - Update sync_group delegation expectation to include soft: false - Stub groups_enabled? in group message handling tests - Update WhatsApp source_id regex expectation for group contact IDs Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * chore: add settings file for additional directories configuration * chore: undo unrelated changes * chore: remove planning doc, fix migration version, fix swagger param consistency - Remove planejamento-chat-interno.md (unrelated planning document) - Fix CreateGroupMembers migration API version from 7.0 to 7.1 - Fix swagger.json: normalize group endpoint paths from {contact_id} to {id} to match YAML sources and existing contact sub-resource conventions Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: CayoPOliveira <cayoproliveira@gmail.com> Co-authored-by: Cayo P. R. Oliveira <cayo@fazer.ai> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>	2026-03-19 21:56:58 -03:00
gabrieljablonski	248d6c23b3	feat: add external_created_at to message creation and update specs for provider callback	2026-02-17 23:32:27 -03:00
gabrieljablonski	9a4c5058f3	Merge branch 'main' into chore/merge-upstream-4.11.0	2026-02-17 23:05:26 -03:00
Gabriel Jablonski	77c90a69ca	feat(whatsapp): delete messages on baileys/zapi providers (#194) ... * feat(baileys): implement message deletion functionality * feat(zapi): add message deletion functionality and corresponding tests * feat(whatsapp): update message deletion logic for provider compatibility * feat(whatsapp): enhance message deletion logic to handle missing phone numbers	2026-01-24 22:37:50 -03:00
Muhsin Keloth	7e4d93f649	fix: Setup webhooks for manual WhatsApp Cloud channel creation (#13278) ... Fixes https://github.com/chatwoot/chatwoot/issues/13097 ### Problem The PR #12176 removed the `before_save :setup_webhooks` callback to fix a race condition where Meta's webhook verification request arrived before the channel was saved to the database. This change broke manual WhatsApp Cloud channel setup. While embedded signup explicitly calls `channel.setup_webhooks` in `EmbeddedSignupService`, manual setup had no equivalent call - meaning the `subscribed_apps` endpoint was never invoked and Meta never sent webhook events to Chatwoot. ### Solution Added an `after_commit` callback that triggers webhook setup for manual WhatsApp Cloud channels	2026-01-19 14:12:36 +04:00
Gabriel Jablonski	c041090675	feat(baileys): upgrade to v7 (#143) ... * feat(baileys): upgrade to v7 (#139) * feat(baileys): v7 * chore(zapi): match baileys changes * test: fix send on whatsapp spec * chore: simplify logic and minor fixes * fix: ensure contact avatar updates when profile picture changes * chore: add beta release workflow * feat: enhance contact update logic to handle conflicts in inbox updates (#140) * feat: update GitHub Actions workflow to trigger on release events and adjust GIT_REF handling * fix: prevent unique constraint error when LID contact inbox already exists (#141) * fix: prevent unique constraint error when LID contact inbox already exists * feat(baileys): handle ephemeral messages	2025-11-13 20:42:08 -03:00
Gabriel Jablonski	4fc80ba4ee	feat(zapi): Z-API integration (#115) ... * feat(zapi): connect flow and UI updates * fix(zapi): re-add manage connection section * feat(zapi): reply * feat: send message * fix: qrcode job logic * test: qr code job specs * chore: concurrent index * chore: whatsapp model minor * test: message window service specs * chore: service refactor * test: zapi service * chore: zapi beta * chore: minor fixes * test: incoming message specs * chore: minor fixes * feat: handle status transitions * test: refactor spec * test: refactor spec * chore(z-api): use feature flag * chore: fix migration name	2025-10-15 16:23:04 -03:00
Gabriel Jablonski	9cd3edb497	fix: revert Twilio message creation using create! instead of create (#118)	2025-10-14 14:43:05 -03:00
Gabriel Jablonski	eaf2f99520	feat: whatsapp cloud service typing status and read messages (#106)	2025-09-02 15:20:13 -03:00
gabrieljablonski	801033bd5f	Merge branch 'main' into chore/merge-upstream-4.5.0	2025-08-20 11:20:31 -03:00
Gabriel Jablonski	99255c199f	feat: on whatsapp baileys check (#95) ... * feat: on whatsapp baileys check * chore: refactoring * chore: refactoring	2025-08-18 12:41:06 -03:00
Gabriel Jablonski	11f8aac294	feat: allow non-admin to refresh baileys connection, and automatically setup connection provider on error (#89) ... * feat: allow non-admin to refresh baileys connection, and automatically setup connection provider on error * Update app/javascript/dashboard/components/widgets/conversation/MessagesView.vue Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * chore: ignore console lint * feat: handle disconnect errors gracefully and update tests accordingly --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>	2025-07-28 20:20:32 -03:00
Tanmay Deep Sharma	8262123481	feat: Remove subscription on WhatsApp inbox delete (#11977) ... - remove webhook subscription while deleting a whatsapp inbox created via embedded signup Co-authored-by: Muhsin Keloth <muhsinkeramam@gmail.com>	2025-07-24 14:04:19 +04:00
gabrieljablonski	4f0b5cd595	Merge branch 'main' into chatwoot/develop	2025-07-16 09:37:08 -03:00
Tanmay Deep Sharma	61d10044a0	feat: Whatsapp embedded signup (#11612) ... ## Description This PR introduces WhatsApp Embedded Signup functionality, enabling users to connect their WhatsApp Business accounts through Meta's streamlined OAuth flow without manual webhook configuration. This significantly improves the user experience by automating the entire setup process. **Key Features:** - Embedded signup flow using Facebook SDK and Meta's OAuth 2.0 - Automatic webhook registration and phone number configuration - Enhanced provider selection UI with card-based design - Real-time progress tracking during signup process - Comprehensive error handling and user feedback ## Required Configuration The following environment variables must be configured by administrators before this feature can be used: Super Admin Configuration (via super_admin/app_config?config=whatsapp_embedded) - `WHATSAPP_APP_ID`: The Facebook App ID for WhatsApp Business API integration - `WHATSAPP_CONFIGURATION_ID`: The Configuration ID for WhatsApp Embedded Signup flow (obtained from Meta Developer Portal) - `WHATSAPP_APP_SECRET`: The App Secret for WhatsApp Embedded Signup flow (required for token exchange)  ## How Has This Been Tested? #### Backend Tests (RSpec): - Authentication validation for embedded signup endpoints - Authorization code validation and error handling - Missing business parameter validation - Proper response format for configuration endpoint - Unauthorized access prevention #### Manual Test Cases: - Complete embedded signup flow (happy path) - Provider selection UI navigation - Facebook authentication popup handling - Error scenarios (cancelled auth, invalid business data, API failures) - Configuration presence/absence behavior ## Related Screenshots:      Fixes https://linear.app/chatwoot/issue/CW-2131/spec-for-whatsapp-cloud-channels-sign-in-with-facebook --------- Co-authored-by: Muhsin Keloth <muhsinkeramam@gmail.com> Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> Co-authored-by: iamsivin <iamsivin@gmail.com> Co-authored-by: Sivin Varghese <64252451+iamsivin@users.noreply.github.com> Co-authored-by: Sojan Jose <sojan@pepalo.com>	2025-07-14 21:37:06 -07:00
Cayo P. R. Oliveira	6a5c0b515d	fix: send receipt to received messages (#70) ... * feat: add received messages handling in WhatsApp services * feat: ensure received messages are processed in the conversation * tests: add received messages specs * tests: add spec for call provider received_messages after save incoming message * test: add spec to prevent calling received_messages for outgoing messages * feat: add received_messages to error handling methods * test: add spec for sending received messages request in WhatsappBaileysService * fix: update fromMe flag in WhatsappBaileysService * test: add spec to verify received_messages is not called for protocol messages * test: improve received_messages stub --------- Co-authored-by: gabrieljablonski <contact@gabrieljablonski.com>	2025-06-17 11:05:28 -03:00
ruslan	b87b7972c1	feat(channel): add support for Telegram Business bots (#10181) (#11663) ... Added support for Telegram Business bots. Telegram webhooks from such bots include the business_message field, which we transform into a standard message for Chatwoot. This PR also modifies how we handle replies, attachments, and image uploads when working with Telegram Business bots. demo: https://drive.google.com/file/d/1Yz82wXBVRtb-mxjXogkUju4hlJbt3qyh/view?usp=sharing&t=4 Fixes #10181	2025-06-16 20:35:23 -07:00
Cayo P. R. Oliveira	a3effacc21	Feat: improve read receipts (#56) ... * feat: add store in additional_attributes to conversation model * feat: set default mark_as_read to true in additional_attributes for conversation params * fix: remove mark_as_read from additional_attributes in conversation * refactor: move message read logic to mark_messages_as_read method in ConversationsController * feat: add 'Mark messages as read' option to WhatsApp channel settings * feat: add 'mark_as_read' option in factorie for WhatsApp channel * feat: integrate Checkbox component for 'mark as read' option in WhatsApp settings * fix: ensure 'mark_as_read' option is included in channel creation payload * feat: add 'Mark as read' settings for WhatsApp inbox, including UI and state management * chore: remove redundant content update test from IncomingMessageBaileysService spec * feat: update 'Mark as read' label to 'Read receipts' and replace Checkbox with Switch component in WhatsApp settings * fix: handle potential nil value for 'mark_as_read' in provider config * feat: refactor provider config to streamline channel creation with 'mark_as_read' option * feat: add test for MESSAGE_READ event dispatch in update_last_seen action * fix: update subheader for 'Mark as read' setting to read receipt behavior in WhatsApp * feat: update mark_messages_as_read behavior to handle false value in provider config * chore: update label for 'Mark as read' option * feat: update update_last_seen to send WhatsApp read receipt for WhatsApp channels * test: remove MESSAGE_READ event dispatch tests in wrong file * feat: enhance update_last_seen behavior for WhatsApp channel to conditionally dispatch messages.read event * feat: update update_last_seen to dispatch messages.read event * test: refactor update_last_seen tests * chore: refactor to ensure provider_service responds to read_messages before ensure the mark_as_read provider config * test: enhance #read_messages with provider config mark_as_read expected behaviors * chore: clarify test names and remove useless expect --------- Co-authored-by: gabrieljablonski <contact@gabrieljablonski.com>	2025-06-03 23:28:15 -03:00
Cayo P. R. Oliveira	548c0351ec	Fix/baileys unread message (#50) ... * fix: correct structure of lastMessages in message content * fix: update send_message to store external_created_at timestamp with result from request * fix: filter incoming messages for unread conversation logic * fix: improve extraction of message timestamp in send_message method * feat: enhance message timestamp extraction and update logic in send_message method * refactor: send_message to improve error handling and update external_created_at timestamp * chore: move message timestamp extraction to helper * fix: use message timestamp extract on incoming * fix: update unread_conversation to handle last message correctly for Baileys provider --------- Co-authored-by: gabrieljablonski <contact@gabrieljablonski.com>	2025-05-23 17:19:01 -03:00
Cayo P. R. Oliveira	21133c3383	feat: mark unread conversations (#49) ... * feat: add MESSAGES_UNREAD event and implement unread action in ConversationsController * feat: rename MESSAGES_UNREAD event to CONVERSATION_UNREAD and update unread action in ConversationsController * feat: implement send_unread_conversation method and update conversation_unread event handling * feat: add test for dispatching conversation.unread event in ConversationsController * feat: add conversation_unread event handling in ChannelListener * feat: add send_unread_conversation method and corresponding tests in Whatsapp channel * feat: add logging for nil last_message in send_unread_conversation method * feat: add send_unread_conversation to error handling methods * feat: implement send_unread_conversation method with logging for nil last_message * fix: add nil check and logging for last_message in send_unread_conversation method * fix: update conversation_unread method to call unread_conversation instead of send_unread_conversation * refactor: rename send_unread_conversation to unread_conversation and update method implementation * refactor: rename send_unread_conversation to send_unread_messages and update implementation to handle multiple messages * refactor: rename send_read_messages to read_messages and send_unread_messages to unread_message for clarity * refactor: rename send_read_messages to read_messages and send_unread_messages to unread_message for clarity * refactor: rename send_read_messages to read_messages for consistency	2025-05-22 11:52:03 -03:00
Cayo P. R. Oliveira	c6e505e924	feat: mark message as read (#43) ... * feat: implement send_read_messages method for WhatsApp channel * feat: implement messages_read event handling and dispatch for conversations * feat: enhance messages_read handling to include last_seen_at and conversation context * feat: update last_seen handling to reference agent_last_seen_at for messages read event * chore: fix rebase * feat: update error handling * feat: update send_read_messages to mark received messages as not sent by the user * test: controller spec * test: channel listener * test: channel and provider --------- Co-authored-by: gabrieljablonski <contact@gabrieljablonski.com>	2025-05-08 11:07:57 -03:00
Gabriel Jablonski	19ad42a580	feat: dispatch to channel listener on availability change (#42)	2025-05-06 20:01:05 -03:00
Gabriel Jablonski	62ef2113d5	feat: toggle typing status on channel provider (#39) ... * feat: toggle typing status on channel provider * refactor: general refactorings * fix: check if channel implements method * test: channel listener specs * test: channel spec * test: baileys service spec	2025-05-03 00:39:39 -03:00
gabrieljablonski	540f67aef6	Merge branch 'fazer-ai/main' into chore/merge-upstream	2025-04-25 16:57:00 -03:00
Cayo P. R. Oliveira	8fc14186e0	feat: process Baileys attachments, fix contact name creation, and handle unsupported messages (#26) ... * fix: return not_found status for missing messages in WhatsApp webhook * feat: enhance message handling to support image attachments * chore: Handle incoming whatsapp baileys service attachments and implement specs for images and videos * fix: add file_content_type method to incoming baileys messages * chore: specs for stickers, audio and files * fix: handle media attachment errors * chore: convert file_content_type to string when attaching media * fix: add handling for attachment not found error in incoming message service * chore: refactor file_content_type method and simplify filename method * chore: update media attachment tests * feat: baileys unsupported message alert (#27) * feat: create alert message for unsupported message types * chore: fail message when try send not supported type in baileys * chore: add tests for unsupported message handling in Baileys service * chore: correct spelling * chore: NIT in spec name * chore: remove unnecessary message reload in unsupported message type test * feat: baileys support to send attachments (#28) * feat: enhance message sending logic with support for attachments and interactive messages * fix: update message format to use messageContent for text messages * feat: attachment message sending * fix: use strict encoding for attachment file download * chore: streamline message sending logic and remove unused error classes * chore: remove type from message sending logic * chore: update message sending specs * chore: raise MessageNotSentError instead of updating message status to failed * chore: change baileys contact name preferences (#30) * refactor: improve contact name handling and extraction from JID * test: enhance message handling to update contact names based on pushName and verifiedBizName * chore: update contact name condition to match phone number from JID * chore: correct method name typo * chore: correct variable names for phone number consistency in tests * chore: update message payload structure and improve error handling in send_message * test: re-add testing for error handling * feat: enhance contact name handling and add self-message detection * fix: ensure presence check for verified business name in contact name retrieval * test: improve specs --------- Co-authored-by: gabrieljablonski <contact@gabrieljablonski.com> --------- Co-authored-by: gabrieljablonski <contact@gabrieljablonski.com> Co-authored-by: Gabriel Jablonski <gabriel@fazer.ai> --------- Co-authored-by: gabrieljablonski <contact@gabrieljablonski.com> Co-authored-by: Gabriel Jablonski <gabriel@fazer.ai> * fix: try to disconnect baileys before destroy inbox (#29) * fix: ensure proper disconnection of Baileys provider on channel destruction * test: add callback tests for disconnecting channel provider in Whatsapp spec * refactor: simplify condition for disconnecting Baileys provider on channel destruction * refactor: enhance disconnect_channel_provider specs for Baileys provider * test: verify channel destruction does not call disconnect_channel_provider --------- Co-authored-by: gabrieljablonski <contact@gabrieljablonski.com> --------- Co-authored-by: gabrieljablonski <contact@gabrieljablonski.com> Co-authored-by: Gabriel Jablonski <gabriel@fazer.ai>	2025-04-25 16:39:17 -03:00
Muhsin Keloth	e0097ab102	chore: Centralize outgoing message reply restrictions for all the channels (#11279)	2025-04-12 08:52:12 +05:30
Gabriel Jablonski	659c3e7c2f	chore: apply Rails/SaveBang cop (#15) ... * chore: apply Rails/SaveBang cop * fix: correct locale validation in category model spec * fix: update save methods to avoid Rails/SaveBang cop violations	2025-04-03 23:29:24 -03:00
Muhsin Keloth	246deab684	feat: Instagram reauthorization (#11221) ... This PR is part of https://github.com/chatwoot/chatwoot/pull/11054 to make the review cycle easier.	2025-04-03 14:30:48 +05:30
Muhsin Keloth	d9450fde4a	feat: Added Instagram channel migration (#11181) ... This PR is part of https://github.com/chatwoot/chatwoot/pull/11054 to make the review cycle easier.	2025-03-26 11:12:32 +05:30
Muhsin Keloth	8826a7066c	chore: Remove delete Instagram story implementation (#11097) ... Currently, Instagram stories are downloaded and displayed as attachments. We previously implemented story deletion by checking individual messages via https://github.com/chatwoot/chatwoot/pull/5300/files#diff-684a16c1b0b4c099fcdfeed95b1820e11fef629fe332ec7ce6a8c600331dd06dR110, but this approach proved impractical and was removed. This PR removes all unused code to avoid confusion. We will revisit the story deletion feature when we implement `instagram_manage_insights`.	2025-03-25 09:44:26 +05:30
Shivam Mishra	650fee58a6	feat: add Google Email fetch and OAuth token refresh service (#9603) ... This PR adds the following changes 1. Add `Imap::GoogleFetchEmailService` and `Google::RefreshOauthTokenService`. The `Google::RefreshOauthTokenService` uses `OmniAuth::Strategies::GoogleOauth2` which is already added as a packge 2. Update `Inboxes::FetchImapEmailsJob` to handle Google inboxes 3. Add SMTP settings for Google in `ConversationReplyMailerHelper` to allow sending emails ## Preview #### Incoming emails  #### Outgoing email  --------- Co-authored-by: Muhsin Keloth <muhsinkeramam@gmail.com>	2024-06-11 14:22:03 +05:30
Sojan Jose	ac93af6028	feat: Support document file uploads on telegram channel (#9266)	2024-05-02 14:05:14 -07:00
Sojan Jose	5f6e17f307	feat: Use Telegram HTML Parsemode (#8731) ... - this ensures that the markdown formatted messages from the Chatwoot dashboard will render consistently in telegram UI for the supported types like bold, italics, links etc	2024-01-18 15:36:36 +04:00
Sojan Jose	76fe2f9bb8	chore: Switch to Markdown instead of MarkdownV2 for telegram channel (#8720)	2024-01-17 14:28:13 +05:30
Nithin David Thomas	d1e7e75638	feat: Adds internal support for markdown in Telegram outgoing messages (#8640) ... This PR adds support for Markdown in the telegram API for send message. The dashboard uses commonmark syntax for markdown but telegram is using MarkdownV2. More info - https://core.telegram.org/bots/api#markdownv2-style Adds support for bold - *bold*, _italic text_, __underline__, ~strikethrough~ Co-authored-by: Sojan Jose <sojan@pepalo.com>	2024-01-16 13:32:59 +04:00
Muhsin Keloth	54bc4c23df	fix: Telegram model specs (#8207)	2023-10-26 00:14:09 +05:30
Muhsin Keloth	4a89bab23a	feat: Handle Telegram send message/attachments errors (#8173) ... Co-authored-by: Pranav Raj S <pranav@chatwoot.com>	2023-10-25 08:36:31 -07:00
Shivam Mishra	b9694a0818	feat: support reply to for Telegram (#8105) ... Co-authored-by: Muhsin Keloth <muhsinkeramam@gmail.com>	2023-10-20 13:14:20 +05:30
Muhsin Keloth	0bc20873f6	feat: Add delivery status for Twilio Channel (#8082) ... Co-authored-by: Pranav Raj S <pranav@chatwoot.com>	2023-10-11 21:17:46 +05:30
Sojan Jose	d93a8d05bc	chore: Increase character limit for external url fields (#7230) ... - Increase the external url field validation to 2048 characters fixes: https://github.com/chatwoot/chatwoot/issues/7098	2023-05-31 19:17:24 +05:30
Sojan Jose	7ab7bac6bf	chore: Enable the new Rubocop rules (#7122) ... fixes: https://linear.app/chatwoot/issue/CW-1574/renable-the-disabled-rubocop-rules	2023-05-19 14:37:10 +05:30
Chamath K.B. Attanayaka	6002394fcf	feat: Support input_select messages on telegram (#5887) ... - Adding interactive button support for telegram for outgoing and incoming messages. Co-authored-by: Sojan Jose <sojan@pepalo.com>	2023-03-28 22:50:07 +05:30
Tejaswini Chile	6013cc9bea	fix: validate instagram story only while saving the message (#6340)	2023-01-30 13:03:59 +05:30
Tejaswini Chile	00cbdaa8ca	Feat: Support for Microsoft Oauth in Email Channel (#6227) ... - Adds the backend APIs required for Microsoft Email Channels Co-authored-by: Pranav Raj S <pranav@chatwoot.com> Co-authored-by: Sojan <sojan@pepalo.com>	2023-01-17 02:39:05 +05:30
Sojan Jose	8ea0660862	chore: Add reauthorization prompt for Whatsapp Channel (#5929) ... - Add reauthorization prompt for Whatsapp Channel fixes: #5782	2022-11-24 14:50:32 +03:00
Pranav Raj S	38776906ab	chore: Generate webhook-verify-token automatically (#5593) ... - Autogenerate webhook verification token in the WhatsAppCloud channel. Co-authored-by: Sojan <sojan@pepalo.com>	2022-10-11 17:32:31 -07:00
Tejaswini Chile	00dc65ef73	fix: Twilio validation over blank messaging_service_sid (#5055)	2022-07-18 20:02:37 +05:30
Sojan Jose	4187428729	chore: Update dependencies to the latest versions (#5033)	2022-07-15 09:51:59 +07:00