Connect N8N with filerun api

Hi Community,

I am trying to build a workflow using the filerun.com API (api :: FileRun Documentation) to automatically name, tag and sort my documents.

Using the proposed CURL POST command from the filerun API, I can access the api and create an access token via a CLI.

However, trying to build an n8n workflow, I run into an error - regardless of what I try.

Trying to create API credentials (Oauth2 API) fails, since the format auf “Authorization Code” seems to differ from the official oauth2, that filerun uses.

I have then tried to create a direct workflow and imported the CURL command into a node, which gets translated as follows (personal information has been “redacted”).

  • The CURL command which works from the CLI and is used 1:1 for importing:

curl -X POST -d “username=n8n&password=redacted$&scope=upload&client_id=redacted&client_secret=redacted&redirect_uri=https://n8n.redacted.de&grant_type=password” https://filerun.redacted.de/oauth2/token/

This is how the import looks in the http-request node:



And this is the error output that I receive:

Can you point me in the right direction of what I am doing wrong and how it needs to be done correctly?

n8n-version: 1.78.1 running in a docker container, no special environment-variables or external databases set.

Thanks,
Thomas

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

That’s not an oAuth 2.0 standard. Use the OAuth 2.0 credentials type

Hi, did you find any luck with setting up filerun with HTTP access?

Hi @nolimits2k @n8n any luck with this issue? Were you able to successfully test HTTPS node with FileRun?

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.