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.Continue reading Send Emails with Tables in Flow – NPSP Example with Payments
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.
Screen two (old version):
And click “Finish” to get this beauty:Continue reading Your Flow Finished
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.Continue reading Unsubscribe Link 2.2
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.Continue reading Upgrade Unsubscribe Link
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.
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.
How to Build your own externally visible Flow
- Create a screen Flow. (This is the hard part).
- Set up My Domain (it’s probably already set up).
- Create a Site domain.
- Create a new Site.
- Create a Visualforce Page to house the Flow.
- Build your link that includes variables for your flow. That looks like:
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.”
When I put in my site domain and the fields are merged in the email, it looks like this:
Read the instructions on the Unsubscribe Link App for details on how to create a Site and Site Domain.
Thanks Alex Edelstein and Narender Singh for building exciting Invokable Apex Actions that extend the use of Flow for admins!
USE CASE: The Ugly Dog Adoption Agency wants to find the 30 dogs who have been at the shelter the longest (minimum 60 days). A Flow will change the picklist “Old Timer” to “Yes” and the staff will then run a promotion for these special doggies. (Don’t worry, Jo Jo Pumpkins! You’ll be on the local news!)
Sometimes as a Salesforce admin I’ve been asked to do things which just seem ridiculously old school, not very efficient and may involve actual paper. When I cannot convince someone to click through a few screens, instead of printing or having an email sent to them, it gets my admin panties all in a bunch. (Wouldn’t that be cool, to have actual admin panties?!)
But when working with a nonprofit, you gotta just let it go. And that is how this printable donor profile came into being.
My pro bono client: The Cedar River Clinics, which are fantastic, independent reproductive & LGBTQ health clinics in Renton, Seattle, and Tacoma.
My task: Create a one-page document with important donor information. The development director will print the doc and hand it to the executive director to review before she calls a major donor. Continue reading Printable Donor Profile
…And building a trigger that creates a new task when an email was sent!
In 2018, I’m focusing on building my “dev cred,” as Leah McGowen-Hare put it at Forcelandia a few years ago.
Next week is the final week of my RAD Women coding course and I am thrilled with how far I have come.
I am also building more connections in the Salesforce digital communities of Trailblazer, Power of Us Hub and Twitter.
So I was checking out the unanswered questions on the Trailblazer Community to see if I could help out and I ran into this one:
Is it possible to use Process Builder or Workflow in auto creating a task after an email is sent related to a record? The email (with a specific Subject filter) will be sent from (A) within Salesforce or (B) Gmail/Outlook but will be recorded in the Activity History. I tried to create a WR but it didn’t run after I sent an email.
The answer to that is ‘No.’ The end. Continue reading Building My Dev Cred