Custom connector for Box Upload API

[Daveyyydave]

Hello!

I am running into an issue creating a custom connector that will upload a pdf file to box folder.  I am configuring the custom connector with the BOX Upload API.  I have postman setup properly to upload file but when I import them to custom connector it does not configure properly.   Below is working postman command that uploads file to box.

 The BOX Upload API uses a post with the body in form-data and two keys, the attributes key and file key.  The attributes key has the file attribute, like file name, what box folderid to put the file in, etc.  I am having a hard time building this part out in custom connectors.

Has anybody here have any success or have done any box custom connector using upload api?  Would appreciate some insights, thanks!

[Daveyyydave]

Might be making some advancements...but think multipart section might be some formatting issue?  Errored is NotFound and output was 404.

[Daveyyydave]

Some more progress, the response is a 400, "API upload did not contain a file part"  So I know its a formatting issue.

My flow details look like this:

The raw request:

{
"host": {
"connectionReferenceName": "shared_box-20upload--",
"operationId": "Uploadfile"
},
"parameters": {
"Content-Type": "multipart/form-data;boundary=WebKitFormBoundary7MA4YWxkTrZu0gW",
"body/$multipart": [
{
"headers/Content-Disposition": "form-data; name=\"attributes\"",
"value": "{\n \"name\": \"test11.pdf\",\n \"parent\": {\n \"id\": \"142982795411\"\n }\n}"
},
{
"headers/Content-Disposition": "form-data; name=\"file\", filename=\"\"",
"value": {
"@odata.type": "#microsoft.graph.fileAttachment",
"id": "AAMkADExNjVhMzg0LWQyMTEtNDNkYi05YWE3LTYwMDk1OGE1YTJmYQBGAAAAAAAbdnwb3G2yR7Pj0aWJn6DTBwBfi9w1M-rwRqySYi6aOKx_AAUvV8t_AABfi9w1M-rwRqySYi6aOKx_AAUzpl0KAAABEgAQACiSHdJ6iRlHqkaX5_xdF3k=",
"lastModifiedDateTime": "2021-12-01T20:58:43+00:00",
"name": "Order_7357678#en-US_Ordered_PacificStandardTime.pdf",
"contentType": "application/pdf",
"size": 102452,
"isInline": false,
"contentBytes": "JVBERi0xLjQ-----etc"
}
}
]
}
}

[Daveyyydave · Accepted solution]

Solved!  This is formatting on the API.  Once formatted correctly, box was able to handle request.

[abc4swc]

@Daveyyydave What was the correct formatting? Running into same issue.

[Shimoyama]

How did you solve it? Running into same issue.

[abc4swc]

@Shimoyama we got it to work with this: 

where "Outputs" in the body is:

binary({"name":"filename","parent":{"id":"folder"}}

[Shimoyama]

Please tell me all the steps to create the flow.
I still get the error.

[abc4swc]

First dynamic input is the filename and varfolder is the folder ID.

The body of the above is:

{

  "grant_type": "client_credentials",

  "client_id": "",

  "client_secret": "",

  "box_subject_type": "enterprise",

  "box_subject_id": "",

  "scope": "root_readwrite"

}

fill in your own client id, client secret and box id.

Then compose using binary of the varBinaryCode.

Full json above:

{

    "type": "object",

    "properties": {

        "access_token": {

            "type": "string"

        },

        "expires_in": {

            "type": "integer"

        },

        "restricted_to": {

            "type": "array"

        },

        "token_type": {

            "type": "string"

        }

    }

}

Then the upload step I already sent that starts with this. 

[S-Young]

@abc4swc is there any chance you could paste the swagger for your connector please?
I'm also struggling to get this going for a custom Box connector, but even after making the suggested changes in this thread, I'm getting the same "code 400" response as you.

[S-Young]

Managed to solve it.

For anyone else struggling, use the swagger below & then adjust your auth mechanism to suit.

swagger: '2.0'
info:
  title: Default title
  description: ''
  version: '1.0'
host: upload.box.com
basePath: /api/2.0
schemes:
  - https
consumes:
  - multipart/form-data
produces: []
paths:
  /files/content:
    post:
      summary: Direct Upload
      description: Direct Upload
      operationId: Direct_Upload
      parameters:
        - name: Content-Type
          in: header
          required: true
          type: string
          default: multipart/form-data; boundary=---MultiPartUploadBoundary
          description: Content-Type
          x-ms-visibility: internal
        - in: formData
          name: attributes
          type: string
          items:
            type: string
          required: true
          description: >-
            An array containing the file name and parent folder id for this
            upload.
        - in: formData
          name: form-data
          required: true
          type: file
      responses:
        default:
          description: default
          schema: {}
definitions: {}
parameters: {}
responses: {}
securityDefinitions:
  oauth2-auth:
    type: oauth2
    flow: accessCode
    authorizationUrl: https://account.box.com/api/oauth2/authorize
    tokenUrl: https://login.windows.net/common/oauth2/authorize
    scopes: {}
security:
  - oauth2-auth: []
tags: []

Then once saved, format the task as follows,

attributes= { "name": "file.ext", "parent":{"id": "targetBoxFolderId"}}

body= the file being uploaded (file content)

form-data= @file.ext, type=file-content-type

[Anonymous]

Does this flow also work for a pdf file type?