Please note: Alfred is now known as Vinton, but this video was recorded prior to the name change.

Video transcript

Let’s take a look at how we can use automation, such as Salesforce flows, to add custom behaviours based on Alfred notes.

You should first watch the Data Models video to understand the data terminology used in Alfred.

In these examples we’ll see how we can add an activity on a contact that is associated with an Alfred audio note.

Here’s a flow we’ve already created. Let’s look in closer detail.

The first thing we’ll look at is this listener associated to the audio object that will listen for every time an audio note has been created or updated, and when the status has transitioned to READY.

The automation gets triggered only when an audio note meets these conditions.

The first thing we’re going to do is we’re going to look at the “video insights”. We fetch all of the fields of the last insight associated with the video that is described in the audio note.

This will be the container of the title, the summary, the next steps and all of that

Once we’ve done that we can navigate to grab all the audio note recipients and we’ll filter down to just the Contacts.

And all of them will then be listed and we’ll get all the records.

Once we have fetched all the audio note recipients that point to a Contact, we bring together all the Contact IDs in an array, which we use to load the actual list of Contact records.

We’ll use the list of Contacts to then create the new activities.

We‘ve prepared a variable which is on the type Record and we call it Activity and we populate

  • the description with the Executive Summary from the audio note.
  • the subject with the title that comes from the insight.
  • We then specify the Who ID standard field on the task with the contact ID.

Then the call type is fixed to Outbound but it could be anything you choose.

And then the due date is a week from when it’s created.

We then add these activities to an array of activities and once we’ve done that we’re going to save the activities.

Once the flow has been saved and activated we can then test it.

Look at this dummy audio note which we manually reverted back to a status of INIT. This is a Call type of audio note which means it’s a meeting recording.

It has a few different participants. We had one Contact and this contact’s record is here but doesn’t have any activities against them.

What I’m going to do now is simulate a change from an INIT status to a READY status and this will manually trigger the flow.

Now if I go back here to my Contact who was a participant of the call, hit refresh, here’s the task created by the flow.

I can see the subject of the task which comes from the title which was automatically detected within the call.

The comments of this task is the executive summary.

And then some of the fields are the ones that we specified in our flow – so due date, priority and a link to the Contact.

Share this video