My goal here is to crete work items whenever an email arrives.
I've successfully created a flow to create a Work Item at my Azure DevOps board when an email arrives.
The issue comes when I try to attach the email attachments to the created Work Item.
Since there isn't any "direct" way to do it with an action, I've tried something like this solution where it proposes use the Azure DevOps API service to attach the attachment.
According to Azure DevOps Api Documentation (here), to attach a file, I should send the binary data as a json, and I've been trying to achieve that with this flow
{
"type": "object",
"properties": {
"Id": {
"type": "string"
},
"Name": {
"type": "string"
},
"ContentBytes": {
"type": "string"
},
"ContentType": {
"type": "string"
},
"Size": {
"type": "integer"
}
}
}
binary(body('Parse_JSON')?['ContentBytes'])
But it doesn't work. Anyone managed to successfully do this? Any hint would be helpful.
Thank you
Hi ,
Maybe we can turn to @Pieter_Veenstra, and there was a section on "send an http request to sharepoint" in his blog. I think if he has time, he might be able to update the blog about "send an http request to Azure DevOps". That will help us a lot.
So, here is what I did on a more granular level, this also now uses MS Flow and not a logic application:
- Create Azure Function to handle uploading/associating an attachment to a DevOps workitem
- This will also need a DevOps API token
- Create an Azure API that will let you access the Azure Function via web request
- Send Attachment data in MS Flow using http request action to the Azure API
Microsoft Flow:
- URI = URL created in Azure API that will hit the azure function
- SubscriptionKey = Key for subscription in Azure API
- Body:
- Attachments - this comes from email trigger (not in pic)
- Subject - this comes from email trigger
- WorkItemId - this comes from 'create work item 2' step so the function knows which work item to work with
Azure Function Code:
#r "Newtonsoft.Json"
using System.Net;
using System.IO;
using System.Text;
using Microsoft.AspNetCore.Mvc;
using Microsoft.Extensions.Primitives;
using Newtonsoft.Json;
public static async Task<IActionResult> Run(HttpRequest req, ILogger log)
{
log.LogInformation("C# HTTP trigger function processed a request.");
string name = req.Query["name"];
string workItemId = req.Query["workItemId"];
string tokenFromDevops = @"{TOKEN}";
string urlDevopsOrgAddAttach = @"https://dev.azure.com/{ORGNAME}/_apis/wit/attachments?api-version=5.0&fileName=";
string requestBody = await new StreamReader(req.Body).ReadToEndAsync();
dynamic data = JsonConvert.DeserializeObject(requestBody);
name = name ?? data?.name;
workItemId = workItemId ?? data?.workItemId;
foreach (var a in data.attachments)
{
string attachmentBytes = a.ContentBytes;
string attachmentFileName = a.Name;
var bytesFromB = Convert.FromBase64String(attachmentBytes);
string url = urlDevopsOrgAddAttach + attachmentFileName;
HttpWebRequest request = (HttpWebRequest)WebRequest.Create(url);
request.KeepAlive = false;
request.Method = "POST";
request.Headers.Add("Authorization", "Basic " + tokenFromDevops);
request.ContentType = "application/octet-stream";
Stream requestStream = request.GetRequestStream();
requestStream.Write(bytesFromB, 0, bytesFromB.Length);
requestStream.Close();
HttpWebResponse response = (HttpWebResponse)request.GetResponse();
var rspUploadAttachment = new StreamReader(response.GetResponseStream()).ReadToEnd();
dynamic jsonResponse = JsonConvert.DeserializeObject(rspUploadAttachment);
String urlUploadedAttachment = jsonResponse.url;
// now we need to associate the uploaded attachment to an actual work item
string urlWorkItem = @"https://dev.azure.com/{ORGNAME}/{PROJECTNAME}/_apis/wit/workitems/" + workItemId + "?api-version=5.0";
HttpWebRequest requestAttach = (HttpWebRequest)WebRequest.Create(urlWorkItem);
requestAttach.Method = "PATCH";
requestAttach.Accept = "application/json";
requestAttach.Headers.Add("Authorization", "Basic " + tokenFromDevops);
requestAttach.ContentType = "application/json-patch+json";
string jsonPatchAttach = @"[
{
'op': 'add',
'path': '/fields/System.History',
'value': 'Adding files from Azure automation'
},
{
'op': 'add',
'path': '/relations/-',
'value': {
'rel': 'AttachedFile',
'url': 'urlReplaceToken',
'attributes': {
'comment': 'Attachment added from Azure automation'
}
}
}
]";
// this can just be done in json above, but left as-is
jsonPatchAttach = jsonPatchAttach.Replace("urlReplaceToken", urlUploadedAttachment);
using (var streamWriter = new StreamWriter(requestAttach.GetRequestStream()))
{
streamWriter.Write(jsonPatchAttach);
streamWriter.Flush();
}
HttpWebResponse responseAttach = (HttpWebResponse)requestAttach.GetResponse();
var rspAddAttachment = new StreamReader(responseAttach.GetResponseStream()).ReadToEnd();
// do whatever you want here with response - or nothing
// dynamic jsonResponse = JsonConvert.DeserializeObject(rspAddAttachment);
}
return name != null
? (ActionResult)new OkObjectResult($"WorkItemID Created!")
: new BadRequestObjectResult("Please pass a name on the query string or in the request body");
}
Helpful resources
Power Platform ISV Studio
ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.
Experience what’s next for Power Automate
See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.
Power Platform Community Conference
Find your favorite faces from the community presenting at the Power Platform Community Conference!
