Import Attachments to Azure DevOps

Integrator.io
1

Has anyone worked with the Azure DevOps API before? Trying to figure out how to import attachments using their REST API. (Attachments - Create - REST API (Azure DevOps Work Item Tracking) | Microsoft Learn)

From my research it appears to want a Base64 string which doesn't currently appear to be natively supported by Celigo.

2

This part can definitely be confusing — when you choose the Azure DevOps connector, there’s no option for "Transfer files into destination application," which is required for handling attachments. We need to add those file upload endpoints to our metadata model (I created an internal ticket for that).

In the meantime, there’s a workaround:

  1. Choose the HTTP connector
  2. Select "Transfer files into destination application"
  3. Then choose your Azure DevOps connection

Set the relative URI to something like:

/{organization}/{project}/_apis/wit/attachments?uploadType=Simple&fileName=imageAsFileAttachment.png&api-version=6.0

Set the request media type to Octet stream. In the Advanced section, set the path to your file’s blob key. If you're pulling the file from a lookup or somewhere other than the default file input, make sure to reference the correct key name (e.g., blobKey, or whatever field holds the file).

I haven’t tested this myself yet, but based on the Azure DevOps docs you linked, this should work with raw binary and doesn’t require Base64 encoding.

Let me know how it goes!

The image shows a form for setting up a destination or lookup, including fields for application type, flow step type, description, and name of the flow step. (Captioned by AI)
The image shows a form for setting up a destination or lookup, including fields for application type, flow step type, description, and name of the flow step. (Captioned by AI)1520×846 42.6 KB

The image shows a software interface for creating an import, with options to name the import, add a description, choose a connection such as "Azure DevOps," and preview or send the request. (Captioned by AI)
The image shows a software interface for creating an import, with options to name the import, add a description, choose a connection such as "Azure DevOps," and preview or send the request. (Captioned by AI)3040×974 165 KB

The image shows a web interface for creating an import on Azure DevOps with an offline connection status and options to name the import, provide a description, and preview or send the request. (Captioned by AI)
The image shows a web interface for creating an import on Azure DevOps with an offline connection status and options to name the import, provide a description, and preview or send the request. (Captioned by AI)3042×1140 227 KB

The image shows a user interface for configuring an HTTP file transfer, including options for method, URL, headers, and request body. (Captioned by AI)
The image shows a user interface for configuring an HTTP file transfer, including options for method, URL, headers, and request body. (Captioned by AI)3032×1668 342 KB

The image shows a user interface for creating a transfer with fields for configuring API headers, media type, HTTP request body, character encoding, and advanced options such as blob key path. (Captioned by AI)
The image shows a user interface for creating a transfer with fields for configuring API headers, media type, HTTP request body, character encoding, and advanced options such as blob key path. (Captioned by AI)1532×1528 143 KB

3

Thanks Tyler, this worked like a charm.

1 Like