# Workflow Outbound Messages

Workflow Rules (along with Process Builders) are now on a deprecation / End-of-Life plan. Existing Workflow Rules will continue to operate for the foreseeable future, but in the near future (Winter 23) Salesforce will begin to prevent creating new Workflow Rules. Establish a plan to migrate to Flows, and create any new automation using Flow Builder. **Outbound Messages are NOT part of the Workflow Rule deprecation plan- you can and should continue to configure and use Outbound Messages when appropriate. Flows can reference and execute these Outbound Messages**

1. An Outbound Message Name ***MUST*** Start with `OM`, followed by a number corresponding to the number of outbound messages on the triggering Object. 2. An Outbound Message Name ***COULD*** contain the Object name, or an abbreviation thereof, in the Field Update Name. This is to avoid different conventions for Workflow Actions in general. 3. An Outbound Message ***MUST*** be named after the Service that it send information to, and then information it sends in the most concise manner possible. 4. The Description of An Outbound Message ***SHOULD*** give precise information on why the Outbound Message is created. 5. Listing the fields sent by the Outbound Message is ***NOT RECOMMENDED***. #### Examples
ObjectEA NameDescription
InvoiceOM01\_Inv\_SendBasicInfoSend the invoice header to the client software.
InvoiceOM02\_Inv\_SendStatusPaidSends a flag that the invoice was paid to the client software.
ContactOM01\_SendContactInfoSends most contact information to the internal Directory.