Are you interested in giving your email recipients the option to unsubscribe from all email that you send out through Salesforce? Please test out the latest version of the Unsubscribe App.
As of February 2024, Google wants bulk senders to allow users to unsubscribe with only one click! That means no more page that says “Are you sure you want to unsubscribe?” You can read more here about how your company organization can get marked as spam if you do not follow this requirement!
If you have already installed the Unsubscribe Link app, I will walk you through how you can update it to meet this requirement. It’s actually easy, I promise. It’s an unmanaged package so I am not able to push changes to you.
Here’s how to update your Unsubscribe Link App:
Go to Setup.
Search for Flows.
Open the flow called Unsubscribe Link.
Click on the blue element Screen: Are you sure
Click the trashcan icon that pops up.
Click on the white dot on the element Decision: Was a record found and drag that to the element Create Records: Create Unsubscribe Record. The text “Yes, Record Found” should pop up.
Click Save As in the top right corner.
In your description you could add that this version includes one-click unsubscribe. Save.
Activate in the top right.
New or having trouble?
If you have not yet installed it, I am currently having trouble modifying the existing app to get it working package because of change in permissions for site guest users for flow. I am trying to install in a dev org and failing to get it work for a site guest user. I am working on a new solution that is based on an Experience Site instead of a Site and that changes how flows are run for users.
If you have an insight on why it is not working currently, contact me via the group below.
Join the Unsubscribe Link Support Group in Trailblazer Community
Ask all your questions and give feedback here. FYI, this project is something I am doing on the side and is not part of my job. If you are interested in helping me maintain and upgrade the app, I would love that! If you have successfully installed the app, you could join the group to answer other people’s questions. Thank you so much!
Thank you
A huge thank you to Brian King who alerted me to this requirement from Google! I am very grateful!
Actually, I don’t know when this change happened, but I just noticed that Flow loops now only have four steps instead of five. The two assignments can now be consolidated into one.
You still have to add the record to a collection, but you can use the same assignment element.
Example 1: Update the record currently in the loop.
Use a Get Records element to create a collection of records to loop through.
Add a loop element
Add ONE assignment element
Update field values for record currently in the loop.
Create a new record collection variable to hold the records you want to update.
Use the same assignment element to add the record currently in the loop to the new collection.
Add an Update Records element to update the records in your new collection.
Follow my blog to keep up to date on Flow and Salesforce
Example 2: Create new records.
Use a Get Records element to create a collection of records to loop through.
Add a loop element
Add ONE assignment element
Create a new record variable (not collection) to hold the values of the new record you want to create.
Assign field values to your new record variable.
Create a new record collection variable to hold your records that you want to create.
Use the same assignment element to add the record currently in the loop to the new collection.
Close the loop.
Add a Create Records element to create the records in your new collection.
Previously step 3 involved two assignment elements!
Watch this recording on Flow loops.
This is how you would combine steps 3 and 4 into one assignment!
Log an email message on the contact record like this one.
UPDATE SUMMER ’23: This is no longer necessary! Read here.
When sending email from a contact record, it magically logs the message to your activity log. In classic, emails were/are automatically logged to the Activities related list. Well, flow doesn’t do that for you. Let me show you how to log it so you and your colleagues know when an email was sent to a contact.
After you add a “Send Email” action to your flow, add two more Create Records elements to the canvas. You will create records of these objects:
Session Description: With Flow becoming the dominant declarative automation tool, business problems we are solving with automation are becoming more complex. We need to be able to build scalable Flows that are easy to maintain, upgrade and troubleshoot, but handling errors in Flows is not always intuitive and user friendly process. Flow Error Handling solution from Salesforce Labs helps Admins to discover Flow errors in faster and more straightforward way. In this session we will show how Admins can use this Salesforce Labs Flow solution to pinpoint exactly where the process went wrong and obtain crucial details of the recorded incident that will help with troubleshooting and fixing the problem in a timely manner.
*Thomas George taught me how to handle flow errors this way when we worked together at Optimum Energy. I love that I got to share it with others through Salesforce Labs.
Stages at the top of the flow screen show your users where they are in the process. It’s simple to set up this progress bar and adds some pizazz to your flow.
Here’s my ordered list to help you get started learning Flow. It includes short and long videos, Trailhead modules and projects, hands-on training and “your turn” challenges to help you stretch what you’ve learned.
The flow will display either a photo or remind you to upload one. On any object!
How It Works:
The Flow looks for a file attached to that record with the title “SalesforcePhoto” (or another phrase of your choosing).
The File gets the title from the name of the file when you upload it. If you upload SalesforcePhoto.jpg, the title becomes “SalesforcePhoto.” You could also open the File details in Salesforce and change the title.
If not found, it asks you to upload a file from your computer named SalesforcePhoto and attaches it to that record. From then on the, the flow displays the photo!
We are using the app because constituents and donors are more than just a record, and seeing their faces humanizes the data.
Invocable methods used with Flow allow you to launch something in an admin friendly format that uses the massive power of Apex. For example, you have an intake screen that collects answers to a few questions, then you use Apex to loop through many related records dispersing those answers in places hard to reach from Flow.
Creating an invocable method in a nutshell: First you write an apex class with @invocable method (label and description) and whatever code you want the apex to do (easy, right?) Then make your Flow including your input and output variables. Then add an Apex action in Flow to send/receive those variables.
Here are some things I learned about sending data between Flow and Apex.
This is NOT an exhaustive list at all. I didn’t try sending a record variable (not just the ID from Flow), but I assume that will work. There are also generic sObjects that are pretty special, but I didn’t try.
