Finally, what I’m able to do is on this latest release of the template, I might want to add something else from Salesforce in order to move the information across. So here I have List Users, I may also want to get some extra information from that user.
For this example, I’ll be filling the contacts from the user list. So here I have Get Contacts by Email. If I want to add a step in here, let’s just do this, I will move my data along like so.
And then within this step I’ll shall set it up so that I’m taking the List Users email address and searching for related contacts.
Now that’s all well and good, but I also need to change what I’m putting into Google Sheets so that I can actually use that information.
Fantastic so now that I put these through, you’ll see that there’s this notification here, saying the source field is from a collection. If there are multiple contacts associated with that one email address, it will go through and add each of them.
So now I run this cycle again.
I go back over to Postman and send my request.
And I should expect to see data moving through this template once again. Although my append release information will be different compared to what it what was sent out before.
So what’s happened with this cycle? Now that it’s finish running lets take a look, we can see the Decision Step last ran six minutes ago. How it would get contacted by email last run two minutes ago. So what’s happened here.
As you can see with this cycle, we have a true and a false exit from Salesforce. When Salesforce returns zero records, as it has done with our previous run, as you can see zero for all seven email addresses, it will exit down this false path, because we don’t have the information that’s required to append it on to our Google Sheet.
This serves the same functionality that a lot of people use decision steps for. However, it’s built into some of our more complicated search methods.