Using Process Builder to set Date field on Contact upon sending Mass Email

Question

So far, I have attempted to build several processes to achieve this using the Process Builder. None of the processes are completing, or firing for all I know, because I don't get an error message if/when it fails. I tried creating workflow rules to help this process along, but to no avail. I don't know enough about Apex to write the code myself, and have been though about two dozen different tutorials and forums trying to scour the internet for a viable answer.

This is what needs to happen: When I send out a Mass Email, a task is automatically created on the person account(contact). This task is given a date, and it is THIS date that I'm trying to auto-populate on the contact page in a custom field labeled "Last Mass Email Sent" (date field).

I would appreciate any help. Thank you.

EDITED FOR MORE INFORMATION

Here is the Process I have built:

START >

Object: TASK ('When a record is created or changed'is checked) >

Criteria: (Conditions are met) [Task].Subject ... 'Starts With' ... ' ... 'String' ... 'Mass Email' (All mass emails start with "Mass Email", making it easy to distinguish.) >

Immediate Actions: Update A Record .. Record: [Task].Name ID (Contact) .. {{From here I have used [formula Today()] [Field Reference: [Task].ActivityDate]}}

I am using the Mass Email Contacts from the Contact tab. I noticed that when the system creates a Task for the mass email, the process builder doesn't recognize it as a created event. When I go in and manually update the Task, the contact gets updated by the Process I built. Something is or isn't happening correctly.

Answer 1

"Mass email actions" are documented as an operation that does not fire triggers.

That's not very specific, but your experience suggests this is one of those actions, as you say

when the system creates a Task for the mass email, the process builder doesn't recognize it as a created event. When I ... manually update the Task, the contact gets updated by the Process

Operations that don't support triggers generally also do not support workflow rules or Process Builder.

One approach to address this would be to use the popular, open source Declarative Lookup Rollup Summaries package. You could build a DLRS rollup in Scheduled mode, with the parameters

Parent Object: Contact
Child Object: Task
Relationship Field: WhoId
Relationship Criteria: Subject LIKE 'Mass Email%'
Relationship Criteria Fields: Subject
Field to Aggregate: ActivityDate
Field to Order By: ActivityDate
Aggregate Operation: Last
Aggregate Result Field: <your target field>

Configure it to run in Scheduled mode every night, and it'll refresh your latest dates on a regular basis. This is a common pattern for doing rollups around non-triggerable activities.