Get File content from github renders the path wrong?

[bjoern]

Hi there,
has anyone stumbled upon the error that the "get File content" block cannot parse the path correctly?

In my case the repository path is Managed/SpaceName/AppName/Appname.qvf
For some reason, when I run the automation, the slashes "/" are converted to %2F
Does anybody know why that happens?
I use the same path variable in the automation for create or update file content to github, and there it is working fine and the path is interpreted with /

[Andrea_Bertazzo]

It seems a problem with encoding:%2F is the encoded form of /.

I assume that the blocks are automatically URL‑encodeing the input: they treat it as a parameter rather than a path.

If the target API expects literal path segments (with / acting as delimiters), encoding / into %2F will cause lookup failures (e.g., it treats the whole thing as a single filename instead of navigating folders).
Try to see if one of these options are available Instead of using the raw path in Get file content:

1. Use “Get item by path” block:
-Input your path: Managed/SpaceName/AppName/Appname.qvf
- This returns the itemId (GUID).

2. Pass the itemId to “Get file content by ID”
-The ID avoids any encoding issues because the API expects it as a unique identifier.