“Here is the use case: sending a family of a deceased relative one letter with all the names of people who have donated in memoriam. So, one letter to the family for many people who gave. Client is a large hospice so this is happening weekly. Open to different options — apps? exports & merge? other? Thanks!”
Well, I’m a few months late, but here you go, Rob. I made a Flow that sends out an email like the one below. I see now that you said “letter”…oops. Hopefully you figured out a solution by now, anyway!
This post is building on the work of the super-smarty Narender Singh aka ForcePanda aka @Nads_P07. With Spring ’21 rich text emails, you can now send tables with lists of child objects.
I followed his tutorial and built two Flow’s specifically using Nonprofit Success Pack (NPSP) objects. The first one is a list of payments and the second is a list of completed volunteer activities. I’ll blog about the second one later. Also on the to-do list is to make one that lists all the gifts received in memory or in tribute to someone else.
Let’s say your organization has 4 (virtual) workshops a year. When a new Contact is created from your website, you want to invite them via email to the NEXT workshop.
We’ll use a record trigger flow and two flow elements to do that. No loop!
Let’s get even fancier: we’ll use Scheduled Paths (#spring21) to send the email three days after the contact is created. Let’s use a formula to make sure the event starts more than six days from now – to give them three days notice before the event.
Are you reading Samantha Shain’s blog The Data Are Alright yet? I LOVE how she talks through all the ups and downs of building her first flow – which is a really complicated one, by the way! She shares her thought processes, her research and her frustrations, pride and other feelings so openly. So if you see an increase in feelings shared here, you know who inspired me!
In Sam’s post, she mentions a few things that she had trouble figuring out. She uses a custom button or link with a URL to pass a record id to a Flow. As she guessed, there is a more elegant way to do it. So elegant even Lady Whistledown would approve.
Look to Miss Daphe Bridgerton, this year’s prize debutante, for the most tawdry yet elegant flow solutions in the ton.
CORRECTION: Sam tweeted “I got it from a Quick Action eventually on my own (I wish I had this resource then), but what I really needed was to pass in a *group* of ids from a list view… which afaik is not possible without code.”
In earlier versions of my Unsubscribe Link app, the “Finish” button would take you a screen that said “YOUR FLOW FINISHED” which many of you pointed out, is less than ideal.
JUNE 7, 2021 UPDATE: Get Unsubscribe Link 3.10 and instructions here. This version has not yet gone through Salesforce Labs Security Review and is not yet on the AppExchange. To switch from 2.2 to 3.10, follow the instructions below on how to uninstall the package. ONLY WORKS IN SUMMER ’21 ORGS!! If 2.2 is working just fine for you, there is no need to change to 3.10.
Unsubscribe Link 2.2 (on AppExchange)
Allow Recipients to Unsubscribe From All Email Sent via Salesforce
When the recipient clicks to unsubscribe, a flow will look for all contacts and leads who have this email in the Email field and mark them “Email Opt Out.” The email address owner will receive one confirmation email immediately. A custom object tracks when someone unsubscribes to allow you to report on it.
See How It Works
UPDATE: 1/28/21 I realized how to send the confirmation email from someone other than “Site Guest User.” More in this post.
This is the third iteration of my app to allow all users to opt out of email sent through Salesforce.
Last week I posted an add-on to the existing app to improve it. Here I have a totally new version with all the bells and whistles.
Could you please install it and test it for me? It should take about 10-15 minutes. After collecting enough feedback, I’ll submit this version to the AppExchange for security review.
I built this really great app to allow email recipients to unsubscribe from all emails sent through Salesforce, but it hasn’t been exactly easy to set up or use. Introducing the first upgrade which makes it much more user friendly!
With the upgrade, your Salesforce users can now pull a merge field into their Lightning and Classic email templates to include the Unsubscribe Link. Bam. No more having to modify and clone confusing email templates.
I’m back from maternity leave and holy SMOKES (get it? The west coast is on fire): an update to Flow in Summer ’20 totally broke the Unsubscribe Link App. It’s okay, though. It’s fixed now and this Flow improvement is worth it.
Here’s my little one disguised as a unicorn
It’s now much simpler to expose a Flow to folks who aren’t logged into Salesforce. They can click a link which launches a Flow that modifies, deletes and creates all sorts of records! (Be careful!)
All you have to do now is save your flow as System Context without Sharing–Access All Data. This eliminates the need to give a Site Guest User permission, adjust your sharing settings, and create sharing rules.
So my example is the Unsubscribe Link. You send an email through Salesforce with this link. Your recipient clicks on it and that launches the Flow which will update their contact and lead records with Email Opt Out. It’s pretty sweet.
In the Unsubscribe Link app, that looks like this. recordId and Email are two variables in my Flow. Everyone who sets up the app will substitute their site domain for “yourSiteDomain.”
Transportation Choices used a web designer to make their Salesforce Web-to-Lead form all fancy.
QUESTION: How can I make the simplest, cheapest “contact us” web form that will generate a new lead record in Salesforce and that people would actually want to use?
BACKGROUND RESEARCH: I’ve tested Salesforce’s web-to-lead many times in free Google Sites, but research indicates most nonprofits are using WordPress.
HYPOTHESIS: A WordPress site and Salesforce’s ancient web-to-lead form will get the job done.
