Speaker 0: Alright. Let me get my screen with that.

Speaker 1: Okay. That came through okay for you, Michelle?

Speaker 0: Yep. Looks great. Yay. K. Hello, MarDreamin. Welcome, everyone. We are so excited to have you joining us today. My name is Michelle from Sercante, and I’m gonna be monitoring today’s session. Before we get started, I do have a couple of housekeeping items to cover. Yes. These sessions are recorded and will be available on demand after the event, and we’ll also be following up with them via email. If you have any questions, go ahead and post them in the q and a tab, and we will try to get to them by the end of the session. Lastly, use the chat. We’ve got emojis, gifs, and more, and we do wanna hear from you. Um, so let’s get started. I’d like to introduce you to our speaker today, Heather, who has, um, some awesome info for you all about simplifying complexity with Salesforce Flows. Take it away, Heather.

Speaker 1: Alright. Thanks, Michelle. Um, uh, happy to be here today. Uh, I hope everyone is joining is enjoying day one so far, margraining. I’ve I’ve had the chance to sit in a couple of sessions this morning, and there were some really good sessions. I know that’s just the start of the conference, so I’m looking forward to seeing what the rest of the conference has to offer. Uh, so first before we get started, uh, of course, I wanna say thanks to our, uh, fantastic sponsors. These are some some great companies with some, uh, awesome tools and services to help a lot of our folks. And, uh, um, yeah. So thanks to everyone for, um, everything they do for our journey. Okay. So today, we’re gonna talk about Salesforce flow. So we’re gonna go a little bit into we’re gonna go cover a little bit of a primer first and talk about some of the basics of flow. Uh, we’ll talk about terminology and, um, some some good things to know about flow up upfront. And then I’m gonna cover off a few scenarios on how flow can help marketing and sales teams. So we’ll just we’ll talk through scenarios and the different ways that, uh, flow can help. We’ll talk about some additional use cases, uh, things to think about. Um, my goal here is to give you an intro to flow and give you enough, uh, inspiration that you can come away from the session and and have a lot of ideas on things that you may wanna do and, um, in your own organization. We’ll also talk about some tips and best practices, and I’ve got some resources at the end too so you can dig in and start learning more. Okay. So flow basics first. So this is my dreaming. This so this is a lot of focus on marketing and marketing automation. So chances are you all are were using or are very familiar with at least one marketing automation tool. I’m gonna say marketing cloud engagement. I’m gonna refer to that, um, quite a bit in this session or Pardot. And, um, you know, that that platform has a lot of great marketing automation features like, you know, completion actions, automation rules, engagement studio. There’s a lot to choose from. However, there are times where there’s some things that you may need to need that account engagement can’t do for you. So when you need to do things like calculations or, um, uh, incrementing values, when you need to copy values, uh, from one field to another or trigger something, uh, on a, you know, field value change, a stage change, um, if you wanna send some custom notifications or update objects other than the prospect itself, uh, this is a thing where this is a situation where you might need a little bit more help, and this is where Salesforce flow can help. Now flow is available on the Salesforce platform, and it is a way to be able to use clicks not code to be able to build out and automate business processes. So you’ll see it looks very familiar or very similar to account engagements, engagement studio programs, but it has a lot of capability to it, um, allows you to, um, create customized user experiences both on the back end and behind the scenes as well as if you want to provide guided guided processes for your users. Um, and also the because they are declarative, which, uh, so that you’re built using using an interface, not coding, you can it’s often easier to manage them rather than having to rely on developer experience to to develop something in Apex. And you’re gonna see today, I have a ton of use cases for you, um, and that’s just scratching the surface. There’s lots that you can do. So we’ll talk about flow types first and when you when you enter when you actually go to create a new flow, this is the screen that comes up. You get to see several, um, options for flow types, but we’re gonna talk about, uh, four in particular. The first we’re gonna talk about is record triggered flows. And this is where you would want to have a background process kickoff when you have made you have our an event occurs on a record. So it’s either changed, it’s either updated or created or deleted. That kicks off actions whether that’s, um, you know, other other record updates or, um, other things like sending an email. Uh, this is a great way to be able to save time by having some manual processes that processes that are manually manual now automated, um, so that you don’t have to rely on somebody to do those steps for you. It also helps to make data entry more consistent because you are not relying on somebody to do that for you, and it can reduce that human error. There’s some scenarios where this may where you may find this useful is creating a task or sending a sending a custom email when a, uh, a lead status, for example, MQL status, uh, um, is updated to MQL. Or if you have an account, for example, then you the address changes, you wanna update all of the related contacts. You can do that with a record triggered flow. Next, we have scheduled triggered flows. So these also run-in the background, but unlike where the record triggered flows that trigger off of a record event, this is gonna run-in the background based on a time interval. So you can set it to run at a specific time or day, um, at, you know, whether it’s daily, weekly, monthly, um, in order to process a set of actions. This is great when you have specific tasks that need to happen at the same time every week, for example, and you don’t have to rely on somebody doing this manually. One one example might be assigning tasks to sales. Uh, this could be very useful, for example, if you are sending a need to send follow-up messages to sales. Maybe you’ve sent them a bunch of MQLs or and those those leads are sitting there and there’s and then we could you could schedule a flow to look at any leads that have not had any activity in x amount of days and schedule an email or a task to be to be sent and assigned to the sales user. Um, that’s just an example. Next, we have auto launch flows, and these are not triggered by a record or a time, but they are, uh, usually invoked by another process. So this is a great way to be able to take a set of actions that you want to occur in multiple processes and leverage them, uh, package them up so that they can be used by those multiple processes. So a great way to to do this is, um, you know, if you have if you wanna be able to handle potential errors in your process, you could package up a an error handling subflow and call that for most of your flows. We’re also gonna talk a little bit about a feature on in account engagement called account, um, external actions. And this is another another way that you can leverage auto launch flows by using external actions on the account engagement side to launch a flow and and can be able to trigger a set of tasks. Lastly is screen flows. So this is, uh, a this lets you create a guided interface in Salesforce for users to be able to walk through a series of steps to update records, create records, um, and it allows that custom tailored experience for them to guide them through steps so that they’re entering information when and how you want them to. So this can really improve the, um, user experience. It definitely improves the of the process and data data, uh, entry. Um, and even just by by the way that you provide the options on in the ScreenFlow, you could reduce the the, you know, the the, um, decisions that, uh, the user has to make when they’re when they’re filling out, you know, deciding what fields have to be filled in or not. The screen flow could do that for you. So what you see here is an example of a lead qualification screen flow. It just basically walks through and, uh, all the user has to do is define what took place and what’s the next step, and it creates tasks automatically. What just hap a task that just occurred and then a task for the feature. Okay. So what you can do in flow, so these are some of the actions or elements that are available to you when you start to build a flow. This is not all of them. This is just most common. So from a data perspective, you can create records or update them, and you can also use the flow to actually go and find records in in the database based on specific, uh, criteria. From a logic perspective, probably the most common element would be the decision element. So this lets you actually set up, uh, defined specific, uh, paths or branches based on criteria, and you can have, uh, one or you can have multiple outcomes or multiple branches depending on the way that you set up your criteria. You can use loops also to be able, if you’re working with a group of records, to iterate and perform perform steps on on one record at a time. And then assignments are a great great way to be able to, uh, assign values to, uh, variables, which we’ll talk about in a sec, that you can use later throughout your flow. You can also set up obviously, in ScreenFlow, you have screens. These are individual interfaces that you can you can actually display record information. You can display text. You can, um, all of the all of the components that you can place on on a screen to make the user experience as good as possible. Actions allow you to be able to perform tasks like sending an email or, um, invoking maybe some custom code in order to perform some steps, uh, in the some additional steps outside the flow, like perhaps auto converting a lead. A subflow is essentially an auto launch flow that I mentioned earlier in terms of subflow types, and you can also have so you can package up those steps and you can call it in in the flow you’re building, like that error handling flow I mentioned. As well as a new feature that’s available, uh, as of winter twenty four, which is the custom error, and this lets you be able to customize the errors that appear. If you have a if you have an error come up in flow, you can handle it in a better manner than just, uh, just a system generated error on screen. I’ll talk about that in a few minutes. Okay. Lastly, I’m gonna go through resources. So these are common resources that are available to you when you’re building flows. This This is just something to keep in mind. I will refer to them a little bit when we’re talking through a little bit of scenarios, but most common ones are the variable, which, um, can is basically a container, stores a value that can be, uh, used throughout your flow. There are several different options, different data types that you can use between text or number or even an actual record. You can store the entire record or multiple. So you can store multiple values in what’s called a collection. Next, we have global variables, which are these, uh, what you see here on screen. And this is sort of system provided information that you can access while you’re in your flow. So in a record triggered flow, for example, you can actually access the details of the record that triggered the flow. Another common use case is, um, to be able to grab the current date and time of the when the flow ran if you need to do any date stamping. You also have formulas. So if you’re familiar with with, um, sales Salesforce formula fields, this is very similar. It allows you to, uh, to calculate information whether that’s a number value, date, for example. A great use case is to be able to set a due date when you’re creating a task, which is sort of the example I have here. And a text template, that’s that’s where you can actually pull together a template of of text that you want to be able to use whether that be in a task, subject, description, email body. You can use you can use it in different places, um, and you cannot just have a stand static text, but you can also pull values from records that are in your flow which can be very useful. The last item I’m going to mention is, um, a couple of features that just to keep in mind because if you’re if you do have account engagement, these these could be features that you could take advantage of. So these are features on the account engagement side but can work with flow. So the so there are external actions which allow you to from you can pair an external action with an auto launch flow in order to, uh, trigger a series of actions either from engagement studio or completion actions. And then external activities allow you to store data in, um, on your prospect from third party systems, but you can leverage that through flow to be able to write that information to your, um, to your prospect in account engagement. Okay. So I’m gonna go through some scenarios on how Flow can help sales and marketing teams, and we’ll walk through each scenario along with some of the tools used and how it was built. So scenario one, we need to be sure that campaigns are activated when created in Salesforce. The status should be updated to completed when they when the campaign wraps up, and that we wanna also put it in a way to automatically make sure that, uh, um, the actual costs are entered so that we make sure we have the we’re able to track ROI. And we wanna be able to do that in a timely manner. So we the tools we can use for this are a record triggered flow, and we can use a feature of record triggered flow called scheduled paths to make this happen. So first, let’s we’ll start with our campaign that gets created in Salesforce. This triggers off a record triggered flow on the campaign that will run that has three paths. So one will run immediately and that’s going to just make sure the campaign is active on creation. The second path is scheduled to run fourteen days after the end date of that campaign, and that will deactivate the campaign. It will turn it will uncheck that active box, and it will also make sure that the status is set to completed. And then it’s also gonna check if actual cost is provided here in this decision. And if it’s not provided, we’re gonna send them an email with, uh, send the owner of the campaign an email to make sure that as a reminder to make sure the actual cost is set up. The last path is another reminder a few day uh, forty five days after that end date just as a check just to make sure that the, um, actual cost was provided. If it wasn’t, it’s gonna send that reminder again. Okay. Scenario number two. We want our enrollment specialist to follow-up with prospects that rest registered for webinar but didn’t attend our session. We need to understand their barriers to entry and potential objections. So we can do this with a record triggered flow, and we can do this using, uh, one of those elements that I mentioned earlier called a loop. So let’s assume that prior to this, we have created, um, leads and contacts. We’ve added them to the campaign, uh, with the status of registered. After the webinar is done, the campaign met campaigns are campaign members, sorry, are updated to either attended or no show depending on how they attended. So that’s done on the background either, um, through through third party integration or through import or some other way. When the campaign is updated and marked completed, we can use a record triggered flow to to trigger it as long as it’s a campaign that’s completed and the campaign type is webinar. We can do use a get element to check if there are any no shows. So that is just double doing a a search of our database to double check any members that are associated with this campaign that have a status of no show. We’re gonna check first, we’re gonna check if there are make sure that there we did find some. If they didn’t find any no shows, that’s great. Then we can just exit the flow and not worry about it. If they did, we’re gonna loop through each member, and we’re gonna use an assignment here where we’re gonna actually start to prepare follow-up tasks for the campaign member. Rather than creating a campaign task each time we go through this loop, we actually wanna just prepare them, uh, and store them, collect them, and then that way we can create them all in one place at the end once we finish our loop. So you can see in this section in my follow-up my prepare follow-up task, I’m actually using several resources in order to make this happen. I’m using a record variable to store all of the values that I want to be in this task. I’m using a formula field in order to determine what that due date should be. For example, if it’s, you know, seven days after the after the, uh, the the current date. Um, and then I’m using some values, uh, from the record that is currently in the loop in order to write some of the other populate some of the other fields. When I have everything I need for that task for that specific campaign member, then I’m gonna store it in my collection, and I’m using a collection variable to store that. Then we’re taking that collection variable, and then I’m telling the flow here, okay. Now we wanna create all of the the follow-up tasks, and we’re gonna do it in one all at one time. We’re gonna create multiple records using this collection variable. Scenario number three. We want to be proactive at engaging members when their membership renewal date is approaching. An opportunity and a task, we want to we want that to be created for, uh, uh, folks thirty days before that expiry date so that they can start reaching out to that prospect that member. We also wanna be able to add them to a renewal nurture until they sign up. So we can do this with, you know, some standard out of the box Salesforce fields like a a formula field. We’ll use a schedule triggered flow, and and we’ll use, um, a third party tool called flow actions for Pardot to help us add them to that nurture. So prior steps, um, would be let’s assume that we’ve created those custom fields. We’ve got one that actually tracks that membership expiry date and then a checkbox, a formula checkbox that’s set to, uh, uh, to be checked when the expiry hits sixty days away. That checkbox is going to be used in a schedule triggered flow that is set to run daily. It’s gonna check for any contacts that have that checkbox set to true. And if that is if they do find that, they’re gonna create a task with some key information. Again, I’m using more resources for this. I’m using formula fields, and I’m using text templates here to be able to see the subject and some values from the record that record that the flow is using right now. I’m creating a opportunity for and tying it to that contact or sorry. Creating an opportunity. And then the next step, I’m actually creating the opportunity contact role because, of course, we wanna make sure that that’s that person is, um, connected there. Next, I’m using a, um, an action from flow actions for Pardot, which allows us to actually reach out to Pardot and say, okay. I have this prospect. I have this person. This is where I wanna add them to a static list. And on the account engagement side, I’m using that static list in order to enter them into a campaign. Scenario four. We want to send an eight week nurture campaign to 20,000 cold prospects. If somebody clicks through, we want our team to follow-up with a Salesforce task. They’ll close it when they get ahold of them, but until that happens, keep emailing them. So we can do this with a few tools. We’ve got a dynamic list that we’re gonna use to manage that manage that nurture and engagement studio program. We’ve got a record triggered flow that’s gonna help us with managing some of this and then also using flow actions for oh, actually, I think that’s a typo of where I don’t think this one includes flow actions for Pardot. So we start out with our dynamic rules. So if you if you’re using account engagement, this is probably familiar to you. So you we have dynamic rules based on status, campaign status. We have some folks that are in here that we want to be, um, that based on their status, they’re being added to a dynamic list. That once they’re added to that list, they’re being entered into an engagement studio program. When they are clicking on the emails, among the some of the actions is creating a task for the salesperson to reach out. And this is just straight out of account engagement. On the in Salesforce, we have our task that we want sales to follow-up with. When they complete that task, this will trigger a record triggered flow that’s set to run on any task associated with this campaign. That task will then check who this would or sorry. That flow will check the lead or the contact that this is related to and then mark their status as contacted. By updating that status, that’s gonna remove them from this dynamic list, and then it’s gonna remove them from the engagement camp engagement studio campaign. Okay. Last scenario. When a lead fills out a form, we wanna trigger a custom email to sales and include detailed instructions on how they should follow-up in a task. And we wanna include form fields in that information so that they they have it or the form form details so they have it. So how do we do this? We can do this using, on the account engagement side, a completion action. We can also we’ll also use an external action and an auto launch flow. So we have on the form side, we are using a conditional completion action set up when a, um, um, when the prospect fills out a form and is a lead. We’re gonna execute an external action and and give that that in uh, external action is gonna call a flow, and it’s gonna give them this information, the email and the ID of that prospect. The auto launch flow gets triggered. We’re first checking just to make sure that we have the ID and, um, so that we can use that ID to find the record associated with the prospect. And then we’re going to create a task for that lead and send an email to sales. So our lead task, we will use we can use some of the information that has been passed from from account engagement, like some of the last form completed information, and then same with the email. Alright. Okay. So that’s five scenarios. So now I have some more. Um, so what what else you can do with Flow? So so, you know, hopefully, this is starting to inspire you and get you anxious to start maybe trying this yourself. So some things to get started if you haven’t built a Flow before, um, may for example, standardizing campaign member statuses on campaign creation. This happens. Right? I mean, we create a webinar campaign, the standard statuses are sent and responded. Those aren’t very ideal. So maybe we wanna standardize those so that we every time a campaign gets created with a type of webinar, we’re creating the making sure that we have the right statuses and not relying on somebody to do those manually. We can date stamp when something happens. Now I know that on the prospect, we can do that on the account engagement side, but maybe we wanna date stamp something that occurs either maybe not in account engagement, maybe maybe it’s something that happens on the Salesforce side, like when a lead changes stages and we can actually track velocity of, um, the movement through stages or through statuses and likewise for opportunity stages. We can make sure that, um, account information is updated when an opportunity is marked close one. Uh, from a marketing perspective, we covered this in our workshop, uh, yesterday. Uh, we had when the opportunity is close one, we mark the customer mark the account as a customer. We looked at the tier, um, or based on the we set a tier of platinum, gold, or silver based on the opportunity amount, and we stamped the, um, the purchase date, so when they became a customer. We can also I mean, we covered off sending custom email or create task, and I think I mentioned this earlier. So we could set up a scheduled flow to actually look at leads that don’t have any activity for a certain amount of time and send them an email. And another one that can commonly come up with when if you have account engagement business units and you’re you’re wanting to take advantage of marketing data sharing is having a flow. You set the criteria that you think that um, that is, um, necessary to make that prospect, uh, sync with or visible in account engagement and use it to set that marketable a marketable field that you can use in that marketing data sharing. Okay. So this there’s more. So this is where you can take things a step further. So you can maybe maybe maybe you wanna be able to track persona based on title. So you can do this with flow based on specific includes or does not include criteria. You can record and track UTM touch points, you whether it’s saving them on a custom object or stamp you know, maybe you wanna save them on the campaign member. Um, you can send information, um, sync information between a an external system. So this can be helpful if you have if you have information you need to get from a like, your ERP, for example. Anything that has, um, a published API. Uh, we talked about using it for guided process, um, and also using it to convert a lead. We looked at external actions earlier, but there’s probably a lot of different use cases that you could use this for. And then also for using, um, third party tools like flow actions for Pardot to be able to have it work directly with Pardot data or perform Pardot admin actions. And I’ve got a QR code here to be able to access flow actions, um, on the AppExchange. I mean, you you’ll get this content anyway that you can reference it later. These are just a few examples of the things you can do. You can also there are also a couple of other, um, AppExchange products that may be useful for, uh, external actions, and these are account engagement automates sort of the series. And one is record creation and the other one that just came out, I wanna say in the last week, is lead reassignment. So you can actually use it. It the the AppExchange products include everything you need. You just have to do a couple steps to turn things on, but the flow is already prebuilt. And, um, you then you have these available to you on the product side. Okay. So, uh, I think we’re good doing okay on time. So I’m gonna go go over a few tips when you’re building. So first, I’m gonna this is gonna be a best practice I’m gonna mention a couple times, but when you are starting your when you are creating your record triggered flow and you are setting your criteria about what records end or enter your your flow, you really wanna be specific about about what those triggers should be about, those entry criteria. Because you don’t want your flow to trigger off of a record when you don’t when when it shouldn’t. So this you’ve got options to be able to do this on the start. Uh, I just got a note saying I had an error. Michelle, do you do you guys still see my screen?

Speaker 0: Yes. I see see everything. You seem to be good.

Speaker 1: Okay. Okay. Good. I’ve done I just wanted to make sure I was still connected. Okay. So so on the trigger side, you have some options on what you what you can, you know, how you can set that criteria. So you can set it based on, um, uh, you know, setting specific act specific credit, uh, conditions that it must meet all the conditions. So, you know, if the field equals a specific value, um, maybe more than one, you can set it to be or or you can set custom condition logic if you think of logic like when you’re doing reports and you have filter logic where you can say, like, one and two or three, um, you can set that here. And then you can even use formulas if you have very specific and very complex criteria. The other element I’ll mention on flow optimization is, uh, fast is is when you’re setting your start criteria, you wanna determine how this is going to trigger, not just when it is, but, um, also how it’s optimized. So there are two options here, fast field updates and actions and related records. You may also hear these referred to as before save and after save flows. So fast field updates will occur, um, um, will these updates will occur on the record that triggered it, and it will happen before the record is saved. So think about, um, a scenario where you have an account that gets created and you have a a record triggered flow that’s that you want to standardize the account name. So you can set that. If that’s the only thing that’s happening on that in that flow is, uh, you can set it to be a fast field update. And when the account is created and the user hits save, that that, um, account name is standardized by the flow before that save is completed. So it all happens in the same transaction. So you would use this if you’re updating fields on the record that triggered the flow itself. That’s the only time you would use this. The other option is actions and related records, and this is where you use, uh, where you would in any other situations where you wanna be able to update or create other records, maybe records that are related to related to the, um, the record that triggered it. Or if you want to send an email or something along that line, you would choose actions and related records. Wherever possible, if you are just making updates on the field itself or on the record itself, fast field updates is highly recommended, um, because especially if you have a lot of flows that are running, um, you you know, it is it is a a way to be able to optimize the performance of your, you know, of your org. I mentioned this earlier, but I’ll highlight this, um, custom error messages. This is something that came out in winter twenty four. This is great for for having better graceful error handling. So you can add this as an element. So if for some reason you have an error, um, maybe you go to create a task and the, um, and maybe you’re assigning it to a user and that user is inactive. You could add an error message on what’s called a fault path, and you can actually specify that, um, you have, you know, like, that that they need to take a look at the user or some some other common, uh, customized message for them. In the in this scenario I’ve got, uh, as an example here, this is triggering when, um, when I when we’re creating an opportunity and the opportune or updating an opportunity to a stage and the, um, and the opportunity doesn’t have a contact role. So triggering that so that, um, it’s it actually would not it it’s almost like a an o like a more sophisticated validation rule just to make sure that they have their these error messages are triggered and guiding the user as much as possible. The messages, I will say as well, is the fact that you can create additional multiple messages. You can specify where they appear, if they’re, uh, in line with the fields or on this or on the like a window, and you can also add resources. So you can actually pull in resources from the record or other information and you can customize them, uh, so they don’t have to be the same the same message across the board. Uh, I think this might be the last tip, um, is flow trigger explorer. So when you’re on your flows page, next to the new flow button is a flow trigger explorer button. This is a great way to be able to see all of the triggered flows that are that are set up in your org by object and by event. So you can see if you’re thinking, well, I think I I think we need a lead. We need a flow for when a lead, you know, status changes or something like that. You can actually go in and take a look. Well, okay. When a lead is updated, these are all the flows that are running, either active or that are available and inactive. So it gives you an idea if there’s something already out there that may be close to what you’re what you’re already looking for and just might might need to have a little tweak or additional action added. So, uh, it’s a good idea to take a look at that before you start building. So with some of these, I’ve already mentioned several times, um, for best practices. Whenever you’re gonna build a flow, it’s a good idea just to kind of, like, figure out the process itself before you start actually getting in there and building. Building. Um, so, you know, whether that’s on a whiteboard or using, you know, like, you know, whatever whatever a Lucidchart or some other tool to be able to just make sure everybody’s on the same page on what’s gonna happen when. And you when you are building, it’s highly recommended you build in a sandbox. You do not want this to run or without being fully tested and and validated, um, and risk impacting your business and your your, uh, business data. I mentioned you wanna be specific about your start conditions and your get elements. So you wanna make sure that you are when you are looking for records in in the database, you wanna make sure that you are very specific about the records that you want to work with, uh, so that it so that when it does pull a record, it’s the one you want. Flow also has, um, features to be able to cut and paste. So if you have a couple of paths and they are essentially performing the same actions, and you there are just some some differences maybe in some of the values, you can actually copy and paste them instead of recreating everything over again so that you can so that it just saves time and speed sync speed things up. Another one is save often. So engagement studio programs in account engagement, uh, you you can create them and they they, you know, they save for you. You don’t have to worry about actually clicking a save button. Flow is not like that. So you want to be able to actually save it early and save often so that you never know when your when your network might fail or when your browser may crash or some other situation or you might get pulled away in time and and it just times out on you. So you definitely wanna save. You wanna be able to test and debug your flows before you activate them. Uh, there are features to do that. We’ve got tool, um, some links to information to help you with that. And then you there is an actual step where you have to actually hit an activate button in order for it to be running and, um, available to be triggered when and where you you are expecting it to. So that’s just something to keep in mind. Alright. So I have a lot of resources here to go through, and this isn’t even a lot this isn’t even all of them, but, uh, if you’re just learning flow or or just, uh, you know, maybe maybe early on in your journey, this is a good place to start. I would say probably with the first couple of items here in Trailhead just to kinda get a little bit of familiarity with flow, then you can start digging in a little bit more and get it get some inspiration from some of these other places. And I’ve got some step by step guides here on how to do some common, uh, how to how to use flow to build some common, um, processes. Alright. So thank you. I hope everyone I hope that was a value, and, um, I guess we can we can tackle some questions.

Speaker 0: Yeah. Absolutely. Thanks, Heather. Um, that was an amazing presentation. We’re gonna do some q and a now. So we do have some questions already. Um, but if you have additional questions, you can hop over to that q and a tab right now, and we can start answering them. Um, so, Heather, one of the first ones, I don’t think we can do it, but, um, I would love if this was a feature. Um, can you make a custom error message and send notifications for Pardot to Salesforce sync errors.

Speaker 1: Well, if somebody else on their team on you there are probably a couple other folks that would probably, um, say to chime in. I I’m pretty sure it’s a no, um, because the only place you can trigger the flow in account engagement is in at least right now, is in a completion action or engagement studio program. And so I don’t think that there’s a way to be able to do that, have a sync error trigger it. But that would be good feedback for the product team.

Speaker 0: Yes. Absolutely. I would love to have that feature. Um, okay. Another question that we have From scenario two about webinars, could you use flow to create webinar campaigns automatically based on third party webinar connector with Pardot, Then use the flow to update member statuses based on the data in Pardot, like attended or absent, then do the flow you showed. Can we do that?

Speaker 1: Yes. Yeah. I mean, like, the how is it gonna depend on the platform? Like so it is it is likely possible based you know, it depends on what the webinar platform is because there would have to be some additional development in order to to be able to tap into the API of that webinar platform. We have done this for, um, uh, with a Zoom integration in order to be able to to do this. Um, I don’t know if, um, Adam’s on, but, um, um, we have folks from our from our, uh, Salesforce or sorry, Sequante Labs team that that could probably weigh in on this a little bit more. But we we have done that where we actually have tied into, um, the webinar and have that execute based on webinar creation and based on the activity of the webinar.

Speaker 0: Awesome. Does anybody have any more questions? Okay. I don’t see any more coming through. Um, so thank you again, Heather, um, for this session, and that concludes the session for today. Um, big thanks to all of our sponsors. If you haven’t had a chance yet, go check them out. We wouldn’t be able to do any of this without them. You are gonna see a quick survey pop up. So if you could take that for us, we would appreciate it. And if not, um, hope to see you guys at more sessions today.

Speaker 1: Thanks, everyone. Enjoy marketing. Thanks, Michelle. Bye.