Send Email Task
The Send Email Task allows workflows to send fully customized email messages with dynamic recipients, subjects, body content, and attachments. It can be used for notifications, updates, approvals, or automated reporting within your processes.

1. Dynamic Recipients
Recipients can be defined dynamically using any of the following options:
- User: Select a specific user in NileDesk.
- User Field: A field on the current form that holds a user.
- Role: All users with a specific Access Role for this process.
- Group: All users in a selected user group.
- Initiator: The user who submitted the document.
- Initiator’s Manager: The manager of the initiator.
- Email Address: A manually entered email address.
- Email Address Field: A text field holding an email address.
- Email Address Expression: An expression that dynamically generates email addresses.
- Step Executor: The user who executed a specific process step.
- Step Executor’s Manager: The manager of the user who executed a step.
- User Expression: A custom expression to calculate recipients dynamically.
Multiple recipients can be combined using any of these methods.
2. Attachments
Emails can include attachments sourced from the process:
- Attachment Fields: Files uploaded into any attachment field on the form.
- PDF Templates: A predefined PDF configured for this process, generated dynamically at runtime.
3. Email Subject
The subject line supports embedded expressions. You can use fixed text or combine it with dynamic fields.
Example:
Email from Item: {{_subject}}
Might render as: Email from Item: Invoice by Victor #11223
4. Email Body
The body supports rich text formatting (bold, italic, colors, lists) and embedded expressions from form fields.
Example:
Dear {{_submitted_by}},
Becomes dynamically:
Dear Victor,
Where Victor is the user who initiated the item that triggered this email.
With this flexibility, emails sent from NileDesk workflows can be highly personalized, context-aware, and automated.
Start Condition Tab
By default, task execute in the order defined in the process diagram. However, you can configure conditions that determine whether this task should run or be skipped. The available options are:
- Always Execute (Default) – The task always runs as part of the sequence.
- Evaluate Condition – Create a visual filter-style condition. If the condition is met, the task executes; otherwise, it is skipped.
- Evaluate Expression – Write a dynamic expression using form fields.
At runtime, if the expression evaluates to
true, the task executes; if not, it is skipped and the process moves to the next step. - Evaluate with AI: For more advanced control over when to execute or skip task, NileDesk allows you to define a natural-language prompt that AI can evaluate using selected context data such as form fields, form tables, or the process timeline. This enables you to describe complex conditions in plain language, allowing AI to intelligently determine whether a specific step should be executed or skipped.