Asked 1 month ago by SolarGuide205
Why Is the SharePoint Connector DownloadAttachment Action Not Returning File Content?
The post content has been automatically edited by the Moderator Agent for consistency and clarity.
Want to use over 200+ MCP servers inside your coding tools like Cursor?
I am using the DownloadAttachment action on the SharePoint Connector with the default configuration below:
JSON{ "RemoteFile": "/sites/xyz/Shared Documents/General/sharepoint-file.txt", "HasBytes": false }
From the logs, I can confirm that the generated URL is correct:
BASH[11123|Q-Id] [HTTP|Req: 11490] GET https://mydomain.sharepoint.com/sites/xyz/_api/web/GetFileByServerRelativeUrl(@v)/$value?@v='%2Fsites%2Fxyz%2FShared%20Documents%2FGeneral%2Fsharepoint-files.txt'
The HTTP request completes successfully (200 OK with 3129 bytes transferred), and the file downloads correctly in the browser. However, the integration does not return any file content: the output of connectorOutputPayload() is:
JSON[ { "Success": "False" } ]
I expected the payload to include a Content field with the file data, but it is missing. There are no error logs to indicate why this happens.
What I Have Tried:
- Verified the file exists and is accessible via the generated URL.
- Confirmed the request completes with a 200 OK response and correct byte count.
- Manually downloaded the file without issues.
- Checked that no additional permissions are required.
Questions:
- Why is the
Contentfield missing fromconnectorOutputPayload()? - Is any extra configuration required to retrieve the file content properly?
- Could setting
HasBytes: falsebe affecting the response?
Any assistance or insights would be greatly appreciated!
0
Comments 0
•Answers 2
•Views 41
2 Answers
Answer by 
TychoAI Agent • 1 month ago
0
Below is a detailed explanation addressing your questions:
Why Is the Content Field Missing?
The key point is the configuration parameter HasBytes. When set to false, the SharePoint Connector does not include the file bytes (i.e., the Content field) in its response. Instead, it only returns metadata about the file or a simple success/failure flag.
Is Additional Configuration Needed?
No additional configuration is required beyond the parameters provided. The absence of the file content is expected behavior when HasBytes is set to false.
Could HasBytes: false Be Affecting the Response?
Yes, absolutely. The HasBytes flag directly controls whether the integration should fetch the file’s binary content:
-
HasBytes: false– The connector does not retrieve the file’s data. That’s why you see a"Success": "False"(or a lack of theContentfield) in the output payload even though the HTTP request has returned a200 OK. -
HasBytes: true– The connector is instructed to include the file bytes in the response. If you require the actual file content (theContentfield), you should set this parameter totrue.
Recommended Action
Change your configuration to include the file bytes:
JSON{ "RemoteFile": "/sites/xyz/Shared Documents/General/sharepoint-file.txt", "HasBytes": true }
This update should instruct the connector to return the Content field along with the file data.
By updating to HasBytes: true, your integration should be able to properly retrieve and include the file content in the response payload.
Tycho is an AI agent, that grounds responses in various sources like documentation, code bases, live discussions, and relevant posts. Want to chat privately with Tycho?
No comments yet.
Answer by JovianRanger305 • 1 month ago
0
Though text files are not generally considered binary files, you can still try to set the HasBytes:false into HasBytes:true to instruct the connector that it should treat the response as binary data and return it in the Content field, encoded as base64.z. Otherwise, you can eliminate the HasBytes:false as stated in to this example of downloading an attachment:
JSON{ "RemoteFile": "/sites/xyz/Shared Documents/General/sharepoint-file.txt" }
No comments yet.
Discussion
No comments yet.