# Send Email

Run the **Send Email** action from a handler.

This action opens the **Salesforce dockable email composer**. It relates the email to the card’s source record. You can prefill recipients, subject, and body.

Use it to send emails without leaving the board.

<figure><img src="https://3097383375-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK2dgObBO5ydOH2ZXDJLa%2Fuploads%2FTWULPIGiR0cwk7P009Zs%2Fimage.png?alt=media&#x26;token=b3d48bb8-6ada-4001-bdcd-3890313cf607" alt=""><figcaption></figcaption></figure>

### Handlers and actions

* **Handler**: defines what happens when a user clicks a Kanban UI element.
* **Action**: an executable operation triggered by the handler.
* **Primary action here**: `Kanban API → Send Email`.
* **Optional follow-ups**: configure extra actions on success or failure.

See [Configuring Handlers](https://docs.flexikanban.ai/standard-kanban/tools/configuring-handlers).

### Configuration

Configure the handler on the interactive element.

**Primary action type**\
`Kanban API`

**Primary action**\
`Send Email`

**Action parameters**\
See below.

### Parameters

The action supports the following parameters.

| Parameter      | Description                                                                                                            |
| -------------- | ---------------------------------------------------------------------------------------------------------------------- |
| **recordId**   | The Salesforce record ID that the email should be related to. Usually this is the ID of the card’s data source record. |
| **toAddress**  | Email address of the primary recipient.                                                                                |
| **ccAddress**  | Email address for CC recipients.                                                                                       |
| **bccAddress** | Email address for BCC recipients.                                                                                      |
| **subject**    | Subject line of the email.                                                                                             |
| **body**       | Email message body that will appear in the composer.                                                                   |

All parameters support **formula expressions**, allowing you to dynamically populate values from fields on the card record.

### Example Use Cases

Typical use cases for this action include:

* Sending an email to a **Contact or Lead directly from a card**
* Contacting an **Opportunity stakeholder**
* Sending follow-up emails from **Case or Request records**
* Prepopulating message templates based on card data

***

### Best Practices

#### Ensure Email Address Is Available

Before allowing users to trigger the **Send Email** action, make sure that the email address used in the `toAddress` parameter is not empty.

If the email field is blank, the email composer will open without a valid recipient, which may lead to confusion for users.

#### Hide the Action When Email Is Missing

A recommended approach is to hide the clickable element when the email address field is empty. This prevents users from triggering the action when it cannot work properly.

You can achieve this by dynamically controlling the element's **CSS style properties** using formula expressions.

For example, configure the **display** CSS property like this:

```
IF(
  ISBLANK({Contact.Email}),
  "none",
  "block"
)
```

With this configuration:

* If the email field is **empty**, the element will **not be rendered** (`display: none`).
* If the email field contains a value, the element will be displayed (`display: block`) and users will be able to trigger the action.

This approach improves the user experience and ensures that the **Send Email** action is only available when it can be executed successfully.

<figure><img src="https://3097383375-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FK2dgObBO5ydOH2ZXDJLa%2Fuploads%2FcE7IfiRxcGKjbH18GpWm%2Fimage.png?alt=media&#x26;token=3c75e3de-9179-4223-903e-b04f43ecb80e" alt=""><figcaption></figcaption></figure>