Skip to content

Commit f95d549

Browse files
Update email-connector.md
Added instructions for sending emails with inline image(s) in an non-interactive way using microflow.
1 parent 053c08a commit f95d549

1 file changed

Lines changed: 8 additions & 0 deletions

File tree

content/en/docs/appstore/use-content/platform-supported-content/modules/email-connector.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -352,6 +352,7 @@ Configuring local clients, such as [Papercut](https://github.com/ChangemakerStud
352352

353353
### Adding Attachments
354354

355+
#### Normal Attachment
355356
To add attachments to the email message, do the following:
356357

357358
1. Create an **Attachment** entity. The **Attachment** entity extends the **FileDocument** entity by making it usable in all the places where the **FileDocument** entity is required.
@@ -360,6 +361,13 @@ To add attachments to the email message, do the following:
360361

361362
2. Set the **Attachment_EmailMessage** association.
362363

364+
#### In-line Attachment
365+
To add in-line attachments to the email message, you can either use the Rich text editor to insert image(s) in the email body. You can also insert in-line attachments non-interactively using a microflow. The steps are to first create an EmailMessage with *Content* property set as below..
366+
```
367+
'before inline image<br><img src="cid:mxcid:test.png" width="530" height="110"><br>after inline image'
368+
```
369+
The img tag's source should be specified using **cid:mxcid** prefix before the source file to have this image added as inline image. Then create Attahcment with the Position attribute set to *ENUM_AttachmentPosition.Inline*. Associate the Attachment with EmailMessage and you should be able to send this email using *SUB_SendEmail* Microflow.
370+
363371
### Page Styling
364372

365373
If the **Email connector** page styling is affected as you select and view email messages, it likely due to errors in the email message CSS. To resolve the errors, turn on **Sanitize email to prevent XSS attacks** in [Account Settings](#other-account-settings).

0 commit comments

Comments
 (0)