I’m not able to get the email integration working at the moment, and I don’t find any mention of this in the docs (might want to add this there once answered :grinning_face_with_smiling_eyes:). So I thought I’d ask here: Does the email integration support “threading”? (grouping of messages on a single topic/chain of replies) If not, does this mean that e.g. every new reply to an email thread will create a new Entity? This seems rather… non-ideal. For me I think I’d actually prefer if it worked like the Discourse integration currently does, and simply updated the Rich Text field with the full contents of the email thread whenever a new message came in. If threading is not supported, is there any suggested approach to make it more manageable to deal with email in Fibery? I’m hoping that this will be solved based on the discussion in “Conversations” for integrations / Email integration and the fact that it is being considered during the Blocks planning and implementation process.

Threads are now supported [image] Sep 5, 2024 / dashing_away Updated Entity View Header & Go-to navigation, Reorder rules & buttons, Lock Whiteboard Changelog This release is dedicated to polishing and small improvements in many areas. metal Updated Entity View Header Entity View header was updated to match new Views headers released last week. Multiple Entity Views switcher is more visible, panel navigation is moved to the right, and you can jump to space fron any entity with a single click. [image] dash Go-to navigation from Entity View We’ve added a Go-to navigation on Entity View (find >> icon in the top right corner). You can quickly jump…

Hi, @Oshyan Thanks for asking. We are going to add threading support after blocks implementation in Fibery. Unfortunately no workarounds are coming to my mind as alternative to handle it right now. Thanks, Oleg

@Oleg, Should we still expect to have thread/conversation support for GMail/IMAP integrations in Fibery?

Hi, @Matt_Blais That is in our plans. Unfortunately we can’t tell exactly when it will be implemented. Thanks, Oleg

just bumping this if there is any development :slight_smile: someone posted that they had programmed a solution with stripping the RE: and then grouping by name or something, but i cannot find it. also wondering if that is something that breaks horribly when sync updates all fields again?

i dont even know if this is something that exists or how to even name this … but a sorting that is begin to sort from the last character (right to left) would be a “workaround” … (which sparks the question if you have support for languages that are right to left …)

[image] dukevannori: someone posted that they had programmed a solution with stripping the RE: and then grouping by name or something, but i cannot find it. also wondering if that is something that breaks horribly when sync updates all fields again? I don’t know if it got posted ever, but I have previously experimented with stripping the RE: FW: etc. from the message subject using regex. It is potentially quite complicated though, because different email clients and different languages give prefixes with a variety of formats. However, if you get such a field working, there’s no reason to think it will break with a sync - you can add fields to an integration database without affecting the fields that are being synced. [image] dukevannori: a sorting that is begin to sort from the last character (right to left) would be a “workaround” If all you wanted to do was sort messages so that ones with the same subject (minus the Re: bits) then reversing the string would be a solution, but it wouldn’t really create a thread. For that, you would ideally need to use an auto-relation that linked all emails to others with the same fundamental subject. [image] dukevannori: which sparks the question if you have support for languages that are right to left We don’t have any specific localisation support. Of course, users can choose to name their databases however they like (with some minor restrictions).

[image] Chr1sG: I don’t know if it got posted ever, but I have previously experimented with stripping the RE: FW: etc. from the message subject using regex. It is potentially quite complicated though, because different email clients and different languages give prefixes with a variety of formats. for this you would work within a formula field or write an automation with a script and then add that self-relation looking for same name of field, correct? would that be something that an AI could solve as well? or would that be a bit too much in regards of cost I was wondering if google is tagging these msgs somehow as replies in their API to get a read out of that … ( i guess there is more to this threads connections than just the Subject field, or inst it?)

[image] dukevannori: for this you would work within a formula field or write an automation with a script and then add that self-relation looking for same name of field, correct? If it were me, I would use a formula field to extract the fundamental subject from the name field, and then I would use auto-relation to link messages together based on them having the same fundamental subject and the same sender. [image] dukevannori: would that be something that an AI could solve as well? or would that be a bit too much in regards of cost It might be possible, but AI is currently rather unreliable/untrustworthy, so I wouldn’t be confident that it had done its job correctly.

The other, simpler, solution would be to adjust the Email integration to include the email headers as a synced field, or at least those headers that are used for thread ID.

[image] Matt_Blais: The other, simpler, solution would be to adjust the Email integration to include the email headers as a synced field, or at least those headers that are used for thread ID. is that something a user can do or does fibery need to do that? [image] Chr1sG: If it were me, I would use a formula field to extract the fundamental subject from the name field, and then I would use auto-relation to link messages together based on them having the same fundamental subject and the same sender. this is the formula I ended up using: Trim(ReplaceRegex(Lower(Name), "^.*(?:re:|aw:|fwd:)", "")) it changes everything to lower case and then looks for the last occurence of either re:, aw: or fwd: and gets rid of that. (chatgpt helped with the regex) then i made a relation many-to-many with the auto match on the formula field. ultimately adding a feed-view of the related msgs to the view and sorting by date. awesome! … now how to strip the “quoted” parts of the msgs … (it never stops hahaha … )

Does email/IMAP support threading? If not, will it ever?

Get Help

mdubakov September 20, 2024, 6:03am 17

Threads are now supported

Topic		Replies	Views
Email integration for CRM use Integrations integration , email-integration	33	3089	September 12, 2026
[DONE] POP3/IMAP Email Integration Connector Integrations email-integration	3	621	September 16, 2021
CHANGELOG: Oct 5 / Email Integration (IMAP), Bug fixes Changelog	8	966	February 9, 2023
"Conversations" for integrations / Email integration Integrations	12	1519	August 6, 2021
Sep 5, 2024 / 💨 Updated Entity View Header & Go-to navigation, Reorder rules & buttons, Lock Whiteboard Changelog	25	522	September 19, 2024

Does email/IMAP support threading? If not, will it ever?

Related topics