Send Email

The Send Email action allows you to send a notification email after a specific trigger is activated. This is a customizable action that enables users to configure the recipient(s), subject, body content, and additional options like attachments and CC/BCC fields.

Configuration Options:

To Whom (Recipient Emails)

• Enter the recipient email addresses in the To Whom field, separated by commas.
• You can also click the "+" button, which opens a modal window with several options:
  • Static Email Address: Manually enter one or more email addresses in a text box.
  • Table Field: Choose a field from the table (based on the trigger) that contains the email addresses of your records.
  • Role: Select a predefined application role whose members will receive the email.
  • System Value: Choose from predefined system options:
    • Created by: Send to the user who created the record.
    • Author of last change: Send to the user who last updated the record.
    • Author of previous change: Send to the user who made the previous change.
    • All users in audit: Send to all users involved in the record’s audit trail.

Add CC/BCC

• You can add additional recipients using the "+ Copy (CC)" button and choose:
  • Copy (CC): To send a copy of the email to other recipients.
  • Blind Copy (BCC): To send a blind copy to recipients (they won't see each other’s email addresses).

Enable Notification for Author of the Change

• Check the "Enable to send a notification to the author of the change if the author exists in the recipients" checkbox to automatically notify the author of the change, if they are part of the recipients list.

Subject

• Enter the subject for the email in the "Subject" field.

Email Template

• Select the type of email template you want to use for the body of the email:
  • Standard System Template: The email body will be filled with a predefined system template based on the selected trigger.
  • Custom Email Body with Standard Template (Frame): Use a rich text editor to create a custom email body, but the email will still use the standard template as the frame.
  • Custom Email Body: Full freedom to design the email body, using the rich text editor, with no predefined frame.

Preserve the "From" Address (Display Name)

• If checked, this will preserve the display name and "from" address for the email as configured in the system.

Send iCal

• Check this box to include an iCalendar (.ics) attachment with the email if required. This is useful for sending calendar events or reminders.

Dynamic Attachments (Optional)

• You can dynamically add attachments to the email by using a function in the Run script step before the Send Email action:
  • Use doo.workflow.attachment.addDynamicAttachment
  • You can attach files in base64 format or files stored within Tabidoo by knowing the internal table name and file ID.
  • These attachments are stored in the doo.workflow.runningData object, and you can remove them by calling doo.workflow.attachment.removeDynamicAttachment or doo.workflow.attachment.clearAllDynamicAttachments.
  • Pay attention to the Foreach loop step - make sure all previous attachments have been removed before sending the next email

Use Case Examples:

• Notify the user who created a record when a related task is updated.
• Send a confirmation email with an attached invoice to a customer after an order is marked as "completed."
• Send a weekly summary to all users in a project, with the content dynamically pulled from the database.

This action allows you to fully customize email notifications, including who receives them, what the content is, and any attachments needed. It also provides flexibility with dynamic email content and recipient handling, making it ideal for automated communication within your workflows.