Sending custom-branded Okta emails from Okta Workflows requires configuring and leveraging a custom domain in the Okta organization. The domain associated with an email depends on how it is triggered, requiring the email to be triggered either by a user on the custom domain or via an API call. Configure a custom domain, create a new Okta connection using that domain, and select it within the workflow to send branded emails.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Okta Workflows

The domain associated with an email depends on how it is triggered. For a user to receive an email associated with a Brand, the email must be triggered either by the user while on the Custom Domain associated with the Brand or via API otherwise it will come from noreply@okta.com. - see How to Send a Branded Activation Email via API on an Org With a Custom Domain

What are the steps to configure in Okta Workflows to send custom branded emails?

Configure a custom domain, create a new Okta connection, and build a workflow that uses the custom domain connection to send branded emails.

1. Configure a custom domain by following the instructions in Configure a custom domain and email address.
2. Create a new Okta connection with the custom domain listed in the Domain section by following the instructions in Create a new connector.
3. Name this connection something that clearly states the custom domain is used.
   Verify the new connection displays the custom domain in the configuration window.
   
4. Create the workflow to send the email, and select the custom domain connection when adding the card.
   NOTE: This example uses the Activate user card.
   Review the workflow card to ensure the custom domain connection is active.
   
5. Confirm the custom domain is selected as the connection for the Activate user card.
   NOTE: Only the card that sends the email requires the custom domain connection. All other cards can use either the default or custom domain connection.
   Check the connection settings on the card to verify the custom domain selection.
   
6. Confirm that the correct name appears in the flow after selecting the custom domain connection to ensure the flow sends emails using the custom domain configured within the tenant.
   Verify the flow displays the updated connection name.
   

Related References

• Configure an Okta Connection Using a Custom Domain in Okta Workflows
• How to Send a Branded Activation Email via API on an Org With a Custom Domain