7 hours 58 minutes
Welcome back In this episode, we're gonna take a look at our first serve Earless option with a logic app demo.
My objectives include just creating a lodge, a cap, and we're gonna create a pretty simple one based on tweets found on Twitter and sending an e mail. But we'll take a look at some further examples And what else is possible using built in work flows that are already available to you
back in the portal Already have our logic APS resource ferreted on the left. So let's go ahead and go into it.
We'll click on add to create our first logic app
and as a mission from the slide, we're gonna use a real basic example. Just a show, how the designer works and what functionality is available to us. So what we're gonna do is take certain tweets from Twitter and send them to an email address.
We're gonna select our existing resource group, leave the location at East us. Then we have another option down here to sin logic app events to the lock analytics workspace.
If you remember, Log analytics can be used to hold metrics and events that are occurring to our resource is this means we can use it to filter and search on events coming out of our logic. App
for a demo. I'm gonna leave this off, So let's go ahead and click on Create
See our new logic cap. So let's go configure it
in our overview page, we're gonna have some examples of some common triggers,
such as when we get a message on our service bus.
When they've incurred resource event occurs,
http request has received. Or when a new tweet is posted, we can also scroll down and take a look at some templates that are already available to us that have several steps in them.
Let's go find the one I'm looking for here.
Email yourself new tweets about a certain key word via outlook.
Since this is using connectors to access, other service is outside of Microsoft. We do need to sign into them so we can use the data from them.
I have a test Twitter account that I'm going to use
next. We're gonna sign into outlook dot com Since we're already signed in using the M s account created earlier in this course, it auto signs us into that outlook dot com account. Let's go and click on Continue
Here. We have the first action and our workflow for when a new tweet appears that we could enter in specific search texts that were looking for.
In our case, I'm going to look for the hashtag Azur,
and we're going to search every five minutes.
Next, it's going to get the user info of who tweeted the tweet. And finally, the next action is going to send an email here. We need to specify what email address we want to send it to.
I'm just gonna send it to ourselves,
and then we can define the subject of the E mail as well as the body
in all these little text boxes. Here are information from the tweet that we can use to create our message body.
If I select in the message body and scroll over to the right, you can see some other options we have for creating content based on the connectors we currently have and other options inside the logic app.
For example, from get user, we can get the user description or location of the user,
and from the tweet itself, we can get a creation time description if it was in reply to somebody else.
We can also create dynamic expressions such as contaminating text or doing simple replace functions on text.
So let me clean this up a little bit,
and we can see our three actions here that we have going on. Let me go ahead and save this.
I'll go ahead and select on run.
Now let's switch over to our alec dot com inbox
and we can see we already have a tweet that came in that had a hashtag Azure, innit?
If we select that email, we can see all the information from our email body that we defined inside the logic app flow. Let's go back to our logic, app, designer
and real quick. I just want to click on New Step
so you can see some of the other actions that we have available to us. For example, we can set variables do language detection.
We can also connect to azure functions as your app service's or logic APS or take a look at http triggers
all this to say there are lots of options for triggers and actions inside of your logic cap and you'll be able to create some very impressive work flows here.
If you click on connectors up here,
it'll take you to a great page describing connectors for azure logic gaps,
including some of the built in triggers and actions that we have,
as well as advanced options for controlling your workload, such as evaluating specific conditions, running for each loops, switch commands or do until loops
that does it for a logic app. Demo. Let's step back to the slides to wrap this up.
Coming up next, we're gonna jump into our next serverless demo by taking a look at your functions. See you in the next episode.