> For the complete documentation index, see [llms.txt](https://docs.ebbot.ai/ebbot-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/actions/send-easit-email.md).

# Send Easit Email

Write the connection's mapped email fields on an Easit item, then update the mapped trigger field to activate the customer's Easit mail rule. Requires the mail field mapping on the connection; the rule itself is configured in Easit.

**Action identifier:** `send_easit_email`.

### Inputs

| Field          | Type           | Required/default | Meaning                                                   |
| -------------- | -------------- | ---------------- | --------------------------------------------------------- |
| `item_id`      | integer        | Required         | Internal Easit item id from the trigger or Get Easit Item |
| `from_address` | string         | Required         | Sender address written to the Ebbot From field            |
| `to`           | string         | Required         | Recipient value written to the Ebbot To field             |
| `subject`      | string         | Required         | Email subject                                             |
| `body_html`    | string         | Required         | HTML email body                                           |
| `cc`           | string \| null | `null`           | Optional Cc value; leave empty to clear it                |

Example input:

```json
{
  "body_html": "<p>Hello, here is our answer.</p>",
  "cc": "",
  "from_address": "support@example.com",
  "item_id": 8708,
  "subject": "Re: your request",
  "to": "customer@example.com"
}
```

### Output

Paths are relative to this action's output. Select them from the builder's variable picker rather than typing them. A field that is null or empty was not returned by Easit; it is not proof that the value is empty in Easit.

| Path            | Type             | Meaning                                                                                       |
| --------------- | ---------------- | --------------------------------------------------------------------------------------------- |
| `success`       | boolean          | Whether content preparation and the trigger update succeeded; does not confirm SMTP delivery. |
| `item_id`       | integer          | Internal numeric Easit Item.id used by GraphQL actions.                                       |
| `prepared`      | boolean          | Whether the mapped mail content was saved or already matched.                                 |
| `triggered`     | boolean          | Whether the mapped mail trigger field was updated successfully.                               |
| `sequence_id`   | integer \| null  | Visible ticket number (Item.sequenceId), when available; not the GraphQL item id.             |
| `triggered_at`  | string \| null   | UTC timestamp written to the mapped trigger field, when available.                            |
| `mapped_fields` | array of strings | Easit field system names configured for this connection mail mapping.                         |
| `error`         | string \| null   | Failure details when the operation did not succeed; otherwise null.                           |

### Behavior and limits

The only outbound-mail action. Supply internal numeric `item_id`, `from_address`, `to`, `subject`, and `body_html`; `cc` is optional. Address formatting must match the customer's mapped Easit fields.

Before use, an Easit administrator must create the mail fields and sending rule and supply their system names for the connection's mail mappings. Body, sender, recipient, subject, and trigger mappings are required; Cc is optional. No field names are assumed across tenants.

The action first writes content fields, then updates the mapped trigger field in a separate mutation. Omitting Cc clears the mapped Cc field when configured. Missing required mappings prevent any write.

Returns `success`, `prepared`, `triggered`, `item_id`, best-effort `sequence_id`, `triggered_at`, `mapped_fields`, and an optional `error`. A successful result confirms the field writes, not SMTP delivery. A failure after preparation may leave saved content.

Use a controlled mailbox for validation. Retrying, including identical content, may intentionally trigger another email. The Easit export rule must exclude workflow-originated changes to prevent loops. Customer replies require Email2GO or another administrator-configured inbound import.

See [Troubleshooting](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/troubleshooting.md), or return to the [action catalog](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/actions.md).
