...
The result of this request takes form of a JSON object, if your request was successful, the JSON object should look something like this:
| Code Block | ||
|---|---|---|
| ||
{
"token_type": "Bearer",
"expires_in": 3599,
"ext_expires_in": 3599,
"access_token": "412076657279206c6f6e67206a756d626c6564207069656365206f662074657874"
} |
...
This "id | userPrincipalName" refers to the ID or "principal name" of the user that will be sending the email. The format of an ID will be a 32 long random string seperated separated into 5 sections, while the format of a principal name will look like an email address. Most emails and IDs will be invalid when palced placed in the request link, to see which emails are allowed, you can check it in your Azure profile.
...
Feed this GET request with a non-expired access token and if the request is successful, you will be presented with an array of JSON objects that represents all of the user's information, including their "User Principal Name" and ID. It is also important to note, this is where that optional API permission "User.Read.All" is used. For this guide, this method will not be used.
After pasting the appropiate appropriate request link, time to feed it the JSON Payload
This JSON payload should consists of simply one JSON object called "message", in the documentation for this API, you could put many properties like custom HTMLs and file attachments. But the only properties that the JSON object must have is only the property "toRecipients", everything else can be left blank or deleted and the request would still be valid, but of course that wouldn't send a proper email, so put the properties you would normally find in an email like a "subject" and "content".
| Code Block | ||
|---|---|---|
| ||
{
"message": {
"subject": "#variable.message_subject#",
"body": {
"contentType": "Text",
"content": "#variable.message#"
},
"toRecipients": [
{
"emailAddress": {
"address": "#variable.recipient_email#"
}
}
],
"ccRecipients": [
]
},
"saveToSentItems": "false"
} |
Enter the appropriate information for each property, you could either hard code the information in the JSON object, or use hash variables like in the code block above.
After the JSON payload, you will also need to insert the request headers. For this request, it needs two things for their header, "Content-type" and "Authorization".
"Content-type" is used so the request knows what type of payload is it using, which for our case is a JSON object, so enter the value "application/json".
"Authorization" as the name suggests is used to authorize the request, this is where you will use your access token, the value for this request header will be a string in the format "[TOKEN_TYPE] [TOKEN]", the type of token we are using will be a "Bearer" token and you can simply copy paste the token or use a hash variable to extract the token that was stored in the workflow variable.
Conclusion
And that's it! With a minimum of 2 JSON Tools, you will be able to send an email using the MS Graph API. By the end, the process of your application should look something like the picture below, 2 tools for requesting an access token and sending the email and any additional activity for automating some of the process, like for the demo app, it is for automating creating the message.
Demo App
Here is the demo app that showcases this guide, please do keep in mind all of the information related to the Azure app has been left empty since those should be filled with your own Azure app. Most of these empty information can be find in the process of the application.
...