Regarding Configure inbound email creation and updates of records

[Avinash_M]

Hello Team,
I have a requirement regarding inbound email updation/creation, so pls check the below requirement:
"As a user, want to ensure no records are created when inbound email is received, however updates are okay, Inbound actions, including flow actions should not be able to create records, but updating of existing records should be permitted.

Can we achieve this by creating a Flow - (as that will execute before an inbound action)  and dropping any action where the email does not contain a watermark".

If the above is achievable through flow designer, could you pls give me the possibilities/steps to configure, Thanks in advance.


Thanks,
Avinash

[pavani_paluri]

Hi @Avinash_M,

If You're not seeing "When email is received" in Flow Designer because the Email Flow Triggers plugin is likely not active.
Go to Plugins, search for Email Flow Triggers(com.glide.email_flow_trigger) and activate it.
After that, refresh Flow Designer, the trigger should now appear.

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for
Kind Regards,
Pavani P

[Avinash_M]

Hi @pavani_paluri,
Thank you for your response, 
I'm not sure why the Email Flow Trigger plugin (com.glide.email_flow_trigger) isn't available in either my enterprise instance or my Personal Developer Instance (PDI). I have checked both, but the plugin doesn’t appear in the list. I do have the Email Filters plugin (com.glide.email_filter) installed, so I’m unsure what’s causing the issue.

Regards,
Avinash

[Avinash_M]

Hi @pavani_paluri 
can you have a look in to this below requirement on the same what we are discussing, if possible give me your inputs:

The existing inbound actions ideally don't need modified.  We need to create a flow which checks if a watermark exists in any inbound email.  If the watermark does not exist, then the email processing should be halted in the flow.  If the watermark does exist, then the flow should allow the email processing to continue to be processed by all flows/inbound actions.

[k_lutz]

Avinash,

Some of the other suggestion seem usable for your use case. If you are only looking for a trigger in a flow I have a suggestion in the attachment. I do wonder how you then plan to lookup the record without a watermark. If someone provides a value in the subject line you would have to parse it out and then use that in a lookup or maybe there is something else you have decided to use in the lookup.

[Avinash_M]

Hi @k_lutz,
Thank you somuch for your reponse, and your approach is helpful, but I need some clarity/inputs, could you pls check the below requirement and give me your thoughts/inputs to achieve:

"The existing inbound actions ideally don't need modified.  We need to create a flow which checks if a watermark exists in any inbound email.  If the watermark does not exist, then the email processing should be halted in the flow.  If the watermark does exist, then the flow should allow the email processing to continue to be processed by all flows/inbound actions."