Newer Version Available
sendEmail()
Immediately sends an email message.
Syntax
For single email messages:
1SendEmailResult = connection.sendEmail(SingleEmailMessage emails[]);For mass email messages:
1SendEmailResult = connection.sendEmail(MassEmailMessage emails[]);Usage
Use this call with Force.com AppExchange applications, custom applications, or other applications outside of Salesforce to send individual and mass email. The email can include all standard email attributes (such as subject line and blind carbon copy address), use Salesforce email templates, and be in plain text or HTML format. You can use Salesforce to track the status of HTML email, including the date the email was sent, first opened, last opened, and the total number of times it was opened. (See “Tracking HTML Email” in the Salesforce online help for more information.)
The email address of the logged-in user is inserted in the From Address field of the email header. All return email and out-of-office replies go to the logged-in user. If bounce management is enabled and SingleEmailMessage.targetObjectId or MassEmailMessage.targetObjectIds is set, bounces are processed by Salesforce automatically, and the appropriate records are updated; otherwise, they go to the logged-in user. Bounce management works for contacts and leads only.
Sample Code—Java
This sample creates an email message and sets its fields, including the To, CC and BCC recipients, subject, and body text. It also sets a recipient to the ID of the logged-in user using the setTargetObjectId method, which causes the email to be sent to the email address of the specified user. The sample creates an attachment and sends the email message with the attachment. Finally, it writes a status message or an error message, if any, to the console.
1public void doSendEmail() {
2 try {
3 EmailFileAttachment efa = new EmailFileAttachment();
4 byte[] fileBody = new byte[1000000];
5 efa.setBody(fileBody);
6 efa.setFileName("attachment");
7 SingleEmailMessage message = new SingleEmailMessage();
8 message.setBccAddresses(new String[] {
9 "someone@salesforce.com"
10 });
11 message.setCcAddresses(new String[] {
12 "person1@salesforce.com", "person2@salesforce.com", "003xx00000a1b2cAAC"
13 });
14 message.setBccSender(true);
15 message.setEmailPriority(EmailPriority.High);
16 message.setReplyTo("person1@salesforce.com");
17 message.setSaveAsActivity(false);
18 message.setSubject("This is how you use the " + "sendEmail method.");
19 // We can also just use an id for an implicit to address
20 GetUserInfoResult guir = connection.getUserInfo();
21 message.setTargetObjectId(guir.getUserId());
22 message.setUseSignature(true);
23 message.setPlainTextBody("This is the humongous body "
24 + "of the message.");
25 EmailFileAttachment[] efas = { efa };
26 message.setFileAttachments(efas);
27 message.setToAddresses(new String[] { "person3@salesforce.com" });
28 SingleEmailMessage[] messages = { message };
29 SendEmailResult[] results = connection.sendEmail(messages);
30 if (results[0].isSuccess()) {
31 System.out.println("The email was sent successfully.");
32 } else {
33 System.out.println("The email failed to send: "
34 + results[0].getErrors()[0].getMessage());
35 }
36 } catch (ConnectionException ce) {
37 ce.printStackTrace();
38 }
39}This example shows how to send an email with the opt-out setting enforced. Recipients are specified by their IDs. The SendEmailOptOutPolicy.FILTER option causes the email to be sent only to recipients that haven’t opted out from email.
1SingleEmailMessage message = new SingleEmailMessage();
2// Set recipients to two contact IDs.
3// Replace IDs with valid record IDs in your org.
4message.setToAddresses(new String[] { "003D000000QDexS", "003D000000QDfW5" });
5message.setOptOutPolicy(SendEmailOptOutPolicy.FILTER);
6message.setSubject("Opt Out Test Message");
7message.setPlainTextBody("This is the message body.");
8SingleEmailMessage[] messages = { message };
9SendEmailResult[] results = connection.sendEmail(messages);
10if (results[0].isSuccess()) {
11 System.out.println("The email was sent successfully.");
12} else {
13 System.out.println("The email failed to send: "
14 + results[0].getErrors()[0].getMessage());
15}Sample Code—C#
This sample creates an email message and sets its fields, including the To, CC and BCC recipients, subject, and body text. It also sets a recipient to the ID of the logged-in user using the setTargetObjectId method, which causes the email to be sent to the email address of the specified user. The sample creates an attachment and sends the email message with the attachment. Finally, it writes a status message or an error message, if any, to the console.
1public void doSendEmail()
2{
3 try
4 {
5 EmailFileAttachment efa = new EmailFileAttachment();
6 byte[] fileBody = new byte[1000000];
7 efa.body = fileBody;
8 efa.fileName = "attachment";
9 SingleEmailMessage message = new SingleEmailMessage();
10 message.setBccAddresses(new String[] {
11 "someone@salesforce.com"
12 });
13 message.setCcAddresses(new String[] {
14 "person1@salesforce.com", "person2@salesforce.com", "003xx00000a1b2cAAC"
15 });
16 message.bccSender = true;
17 message.emailPriority = EmailPriority.High;
18 message.replyTo = "person1@salesforce.com";
19 message.saveAsActivity = false;
20 message.subject = "This is how you use the " + "sendEmail method.";
21 // We can also just use an id for an implicit to address
22 GetUserInfoResult guir = binding.getUserInfo();
23 message.targetObjectId = guir.userId;
24 message.useSignature = true;
25 message.plainTextBody = "This is the humongous body "
26 + "of the message.";
27 EmailFileAttachment[] efas = { efa };
28 message.fileAttachments = efas;
29 message.toAddresses = new String[] { "person3@salesforce.com" };
30 SingleEmailMessage[] messages = { message };
31 SendEmailResult[] results = binding.sendEmail(messages);
32 if (results[0].success)
33 {
34 Console.WriteLine("The email was sent successfully.");
35 }
36 else
37 {
38 Console.WriteLine("The email failed to send: "
39 + results[0].errors[0].message);
40 }
41 }
42 catch (SoapException e)
43 {
44 Console.WriteLine("An unexpected error has occurred: " +
45 e.Message + "\n" + e.StackTrace);
46 }
47}This example shows how to send an email with the opt-out setting enforced. Recipients are specified by their IDs. The SendEmailOptOutPolicy.FILTER option causes the email to be sent only to recipients that haven’t opted out from email.
1SingleEmailMessage message = new SingleEmailMessage();
2// Set recipients to two contact IDs.
3// Replace IDs with valid record IDs in your org.
4message.toAddresses = new String[] { "003D000000QDexS", "003D000000QDfW5" };
5message.optOutPolicy = SendEmailOptOutPolicy.FILTER;
6message.subject = "Opt Out Test Message";
7message.plainTextBody = "This is the message body.";
8SingleEmailMessage[] messages = { message };
9SendEmailResult[] results = binding.sendEmail(messages);
10if (results[0].success)
11{
12 Console.WriteLine("The email was sent successfully.");
13} else {
14 Console.WriteLine("The email failed to send: "
15 + results[0].errors[0].message);
16}BaseEmail
| Name | Type | Description |
|---|---|---|
| bccSender | boolean | Indicates whether the email sender receives a copy of the email that is sent. For a mass mail, the sender is only copied on the first email sent. |
| saveAsActivity | boolean | Optional. The default value is true, meaning the email is saved as an activity. This argument only applies if the recipient list is based on targetObjectId or targetObjectIds. If HTML email tracking is enabled for the organization, you will be able to track open rates. |
| useSignature | boolean | Indicates whether the email includes an email signature if the user has one configured. The default is true, meaning if the user has a signature it is included in the email unless you specify false. |
| emailPriority | picklist | Optional. The priority of the email.
|
| replyTo | string | Optional. The email address that receives the message when a recipient replies. This cannot be set if you are using a Visualforce email template that specifies a replyTo value. |
| subject | string | Optional. The email subject line. If you are using an email template and attempt to override the subject line, an error message is returned. |
| templateId | ID | The ID of the template to be merged to create this email. |
| senderDisplayName | string | Optional. The name that appears on the From line of the email. This cannot be set if the object associated with a OrgWideEmailAddressId for a SingleEmailMessage has defined its DisplayName field. |
SingleEmailMessage
The following table contains the arguments single email uses in addition to the base email arguments.
| Name | Type | Description |
|---|---|---|
| bccAddresses | string[] | Optional. An array of blind carbon copy (BCC) addresses or object IDs of
the contacts, leads, and users you’re sending the email to. The maximum
number of bccAddresses is 25. This argument is allowed
only when a template is not used. You can specify opt-out email options with the optOutPolicy field only for those recipients who were added by their IDs. Email addresses are verified to ensure that they have the correct format and haven’t been marked as bounced. If the BCC COMPLIANCE option is set at the organization level, the user cannot add BCC addresses on standard messages. The following error code is returned: BCC_NOT_ALLOWED_IF_BCC_COMPLIANCE_ENABLED. All emails must have a recipient value in at
least one of the following fields:
|
| ccAddresses | string[] | Optional. An array of carbon copy (CC) addresses or object IDs of the
contacts, leads, and users you’re sending the email to. The maximum number
of ccAddresses is 25. This argument is allowed only
when a template is not used. You can specify opt-out email options with the optOutPolicy field only for those recipients who were added by their IDs. Email addresses are verified to ensure that they have the correct format and haven’t been marked as bounced. All emails must have a recipient value in at
least one of the following fields:
|
| charset | string | Optional. The character set for the email. If this value is null, the user's default value is used. Unavailable if specifying templateId because the template specifies the character set. |
| documentAttachments | ID[] | Deprecated. Use entityAttachments instead. Optional. An array listing the ID of each Document you want to attach to the email. |
| fileAttachments | EmailFileAttachment[] | Optional. An array listing the file names of the binary and text files you want to attach to the email. You can attach multiple files as long as the total size of all attachments does not exceed 10 MB. |
| entityAttachments | ID[] | Optional. Array of IDs of Document or ContentVersion items to attach to the email. |
| htmlBody | string | Optional. The HTML version of the email, specified by the sender. The value is encoded according to the specification associated with the organization. |
| inReplyTo | string | Optional. The In-Reply-To field of the outgoing email. Identifies the emails to which this one is a reply (parent emails). Contains the parent emails' Message-IDs. See RFC2822 - Internet Message Format. |
| optOutPolicy | SendEmailOptOutPolicy (enumeration of type string) |
Optional. If you added recipients by ID
instead of email address and the Email Opt Out
option set, this field determines the behavior of the sendEmail() call. The opt-out settings
for recipients added by their email addresses aren’t checked and those
recipients always receive the email. Possible values of the SendEmailOptOutPolicy enumeration
are:
|
| orgWideEmailAddressId | ID | Optional. The object ID of the OrgWideEmailAddress associated with the outgoing email. OrgWideEmailAddress.DisplayName cannot be set if the senderDisplayName field is already set. |
| plainTextBody | string | Optional. The text version of the email, specified by the sender. |
| references | string | Optional. The References field of the outgoing email. Identifies an email thread. Contains the parent emails' Message-ID and References fields and possibly In-Reply-To fields. See RFC2822 - Internet Message Format. |
| targetObjectId | ID | Optional. The object ID of the contact, lead, or user the email will be
sent to. The object ID you enter sets the context and ensures that merge
fields in the template contain the correct data All emails must have a recipient value in at
least one of the following fields:
|
| toAddresses | string[] | Optional. An array of email addresses or object IDs of the contacts,
leads, or users you’re sending the email to. The maximum number of
toAddresses is 100. This argument is allowed only
when a template is not used. You can specify opt-out email options with the optOutPolicy field only for those recipients who were added by their IDs. Email addresses are verified to ensure that they have the correct format and haven’t been marked as bounced. |
| treatBodiesAsTemplate | boolean | Optional. If set to true, the subject, plain text, and HTML text bodies of the email are treated as template data. The merge fields are resolved using the renderEmailTemplate() call. Default is false. |
| treatTargetObjectAsRecipient | boolean |
Optional. If set to true, the
targetObjectId (a contact, lead, or user) is the
recipient of the email. If set to false, the targetObjectId is supplied
as the WhoId field for template rendering but isn’t
a recipient of the email. The default is true. This field is available in API version 35.0 and later. In prior versions, the targetObjectId is always a recipient of the email. |
| whatId | ID | Optional. If you specify a contact for the
targetObjectId field, you can specify a
whatId as well. This field helps to further ensure
that merge fields in the template contain the correct data. The value must
be one of the following types:
|
MassEmailMessage
The following table contains the arguments mass email uses in addition to the base email arguments.
| Name | Type | Description |
|---|---|---|
| description | string | A value used internally to identify the object in the mass email queue. |
| targetObjectIds | ID[] | An array of object IDs of the contacts, leads, or users the email will be sent to. The object IDs you enter set the context and ensure that merge fields in the template contain the correct data. The objects must be of the same type (either all contacts, all leads, or all users). You can list up to 250 IDs per email. If you specify a value for the targetObjectIds field, optionally specify a whatId as well to set the email context to a user, contact, or lead. This ensures that merge fields in the template contain the correct data. |
| whatIds | ID[] | Optional. If you specify an array of contacts for the
targetObjectIds field, you can specify an array of
whatIds as well. This helps to further ensure that
merge fields in the template contain the correct data. The values must be
one of the following types:
|
EmailFileAttachment
The following table contains properties that the EmailFileAttachment uses in the SingleEmailMessage object to specify attachments passed in as part of the request, as opposed to a Document passed in using the documentAttachments argument.
| Property | Type | Description |
|---|---|---|
| body | base64 | The attachment itself. |
| contentType | string | Optional. The attachment's Content-Type. |
| fileName | string | The name of the file to attach. |
| inline | boolean | Optional. Specifies a Content-Disposition of inline (true) or attachment (false). In most cases, inline content is displayed to the user when the message is opened. Attachment content requires user action to be displayed. |
Response
Fault
The following API status codes can be returned. Also, sendEmail() can return other errors when rendering email templates. See renderEmailTemplate() Faults.
BCC_NOT_ALLOWED_IF_BCC_COMPLIANCE_ENABLED
BCC_SELF_NOT_ALLOWED_IF_BCC_COMPLIANCE_ENABLED
EMAIL_NOT_PROCESSED_DUE_TO_PRIOR_ERROR