> For the complete documentation index, see [llms.txt](https://docs.veza.com/4yItIzMvkpAvMVFAamTf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veza.com/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/policies-workflows/actions/write-back-email.md).

# Write Back Email

Updates HRIS or identity source systems with email addresses created by previous [Create Email](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/policies-workflows/actions/create-email.md) actions in the same workflow. This ensures the source of identity (such as Workday) has the employee's new corporate email address, keeping records consistent across systems.

**Example Use Cases:**

* After creating an Exchange Server mailbox during onboarding, write the new email address back to the Workday Worker record
* Update an OAA-based HRIS source with email addresses generated by provisioning workflows

| Setting     | Description                                                                                     |
| ----------- | ----------------------------------------------------------------------------------------------- |
| Entity Type | The HRIS or identity source entity type to update with the email address (e.g., Workday Worker) |

**Supported Integrations:**

| Integration     | Notes                                                                                |
| --------------- | ------------------------------------------------------------------------------------ |
| Workday         | Writes email to the Worker record via the Workday API                                |
| Oracle HCM      | Writes email to the Oracle HCM employee record                                       |
| Hi Bob          | Writes email to the Hi Bob employee record                                           |
| OAA Custom HRIS | Writes email to custom HRIS identity providers integrated via Open Authorization API |

{% hint style="info" %}
Write Back Email is specifically designed for HRIS / identity source systems. It is not used to update email attributes in target applications like Active Directory or Okta — use [Sync Identities](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/policies-workflows/actions/sync-identities.md) with email attribute transformers for that purpose.
{% endhint %}

### Example: Exchange Server onboarding with email write-back

In a typical Workday-to-Active Directory onboarding workflow, Write Back Email is the third step:

1. **Sync Identities** — creates the AD user account from the Workday Worker
2. **Create Email** — creates an Exchange Server mailbox (generates the email address)
3. **Write Back Email** — writes the new email address back to the Workday Worker record
4. **Sync Email to AD** — syncs the email attribute to the AD user account

This ensures that the Workday record reflects the employee's corporate email immediately after onboarding, without manual HR data entry.

For the full workflow configuration, see the [provisioning example](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/policies-workflows/actions.md#example-conditions-and-actions-provisioning-to-active-directory) in the Actions overview. For Exchange Server setup, see [Exchange Server Provisioning](/4yItIzMvkpAvMVFAamTf/integrations/integrations/exchange-server/provisioning.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.veza.com/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/policies-workflows/actions/write-back-email.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.