Activity Capture logs every email it captures to Salesforce as either a Task or an EmailMessage record. You can choose one per Activity Capture configuration. Most customers choose EmailMessage, because it keeps the full email. Choose Task if your Salesforce reports are built on Tasks.
Note: EmailMessage needs Enhanced Email switched on in Salesforce. Without it, Weflow can only log your emails as Tasks.
Task vs EmailMessage overview
In Salesforce | Task | EmailMessage |
Sender and recipients | Not stored | From, To, Cc and Bcc fields |
Email body and thread | No thread | Full HTML body and thread |
Standard activity reports | Included alongside Events | Included alongside Events |
Editing after logging | Editable | Cannot be edited, even via API |
Storage per email | About 1.8 kB per Task | About 7x a Task |
Use in reporting | Standard reports, workflows and automations | Reports need joins to related objects |
Record association | WhoId and WhatId | WhoId, WhatId, ParentId and EmailMessageRelation |
Note: Weflow's own views read both objects. Your choice changes what you can report on inside Salesforce, not what Weflow shows you. Email open tracking works with both Task and EmailMessage. It needs Weflow's analytics package installed in Salesforce, which itself needs Enhanced Email, and it tracks emails sent from the Weflow add-in.
When to choose Task or EmailMessage for Activity Capture
Choose EmailMessage if you need the full email content, attachments and thread in Salesforce, for compliance or context.
Choose Task if your reports, dashboards and automations are built on Tasks.
Logging Activity Capture emails as Tasks
A Task is a standard Salesforce activity, so your captured emails appear in standard activity reports alongside Events and work with your existing workflows and automations. If your org uses Task record types, you can set a default record type so captured emails land in the right one.
Note: Weflow sets Type = Email on every email it logs as a Task, so you can filter your emails apart from calls, meetings and follow-ups in your reports and dashboards.
Limitations of logging emails as Tasks
No sender or recipients: a Task does not store From, To, Cc or Bcc, so you cannot report on who sent or received an email.
No thread: You lose access to native threading, reply tracking, and detailed email metadata that EmailMessage provides.
Attachments without context: attachments are logged without the full email context or thread.
Logging Activity Capture emails as EmailMessage
EmailMessage is the dedicated Salesforce object for storing email records. It allows you to store the full email: From, To, Cc and Bcc in native fields, the full HTML body, the thread and the attachments.
One record relates to up to 50 recipients, so an email you send to a customer with three colleagues copied is one record, shown on you, each colleague, the contact and the account.
Note: Salesforce sets Status = Sent on every logged EmailMessage. The field has no Received value, so it does not tell you whether an email was inbound or outbound.
Limitations of logging emails as EmailMessage
Cannot be edited: Salesforce does not allow a sent EmailMessage to be edited, even through the API. To move one to another record, unlog it and log it again.
More storage: An EmailMessage takes about seven times the storage of a Task.
Learn more about how to reduce EmailMessage storage in Salesforce.
How to switch the Activity Capture logging object between Task and EmailMessage
A Salesforce admin can change the logging object in Weflow's Admin Console at any time. The change applies to the emails Weflow logs from then on. Emails already logged keep the object they were logged as.
In Weflow, go to Admin Console > Activity Capture.
Open the configuration you want to change.
On the General settings tab, under Select object type to log emails to, choose Email Message or Task.
If you chose Task, pick the record type for your captured emails in the setting below it, or leave it set to None if your org does not use record types for tasks.
Click Save changes.
How to move an email logged as EmailMessage to another record
Salesforce does not allow a sent EmailMessage to be edited, so Weflow moves it by deleting it and logging it again.
Open the email in Outlook with the Outlook Add-In, or in Gmail with the Chrome Extension.
Unlog the email.
Log it again against the right record.
The new record keeps the email's own date, so reports built on message date do not change. Reports built on created date show the email on the day you moved it. An email logged as a Task can be edited in Salesforce instead.
Frequently asked questions about Task and EmailMessage logging
How do I find the emails Weflow logged as Task or EmailMessage?
Every EmailMessage Weflow logs has a Message ID starting with W_, so a report filtered on it shows only Weflow's emails. Tasks have no Message ID: filter on the Weflow integration user in Created By. Insights in Weflow also lists each user's captured emails.
Does an EmailMessage update Last Activity Date in Salesforce?
Weflow logs the email as the EmailMessage record alone and creates no extra record alongside it, so Last Activity Date updates the way Salesforce updates it for EmailMessage.
Can an email be logged twice if another tool also logs it to Salesforce?
Weflow checks the message ID before logging, so it never creates a second copy of its own records. It cannot guarantee the same for emails another tool logged, because that depends on how the other tool stored them. Switch off email logging in the other tool before you start Activity Capture.
