Generic OAuth 2.0 Credential + Http Request Not Working

[vinicius_carrara]

Describe the problem/error/question

I’m trying to set a generic credential to connect to Adobe Workfront using OAuth 2.0 flow. the authorization on Adobe is working fine, when I test the credential the login page shows up and I’m able to connect the account

The problem is happening when I try to request any endpoint, it’s showing Node error:

this is the documentation of Adobe workfront:

Authentication Method:

Authorization code flow for custom OAuth 2 applications | Adobe Workfront

Api Request: API basics | Adobe Workfront

What is the error message (if any)?

Please share your workflow

Share the output returned by the last node

{
“errorMessage”: “Cannot read properties of undefined (reading ‘split’)”,
“errorDetails”: {
“rawErrorMessage”: [
“Cannot read properties of undefined (reading ‘split’)”
]
},
“n8nDetails”: {
“nodeName”: “Project Request”,
“nodeType”: “n8n-nodes-base.httpRequest”,
“nodeVersion”: 4.2,
“itemIndex”: 0,
“time”: “10/03/2025, 13:42:22”,
“n8nVersion”: “1.78.1 (Self Hosted)”,
“binaryDataMode”: “default”,
“stackTrace”: [
“NodeApiError: Cannot read properties of undefined (reading ‘split’)”,
" at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/HttpRequest/V3/HttpRequestV3.node.js:525:33)“,
" at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:633:19)”,
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:882:51",
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:1216:20"
]
}
}

Information on your n8n setup

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

[ThinkBot]

Quite odd. The split error implies something is null and trying to call split on it. But I don’t see it in your setup. It may be within the node itself.

We had a similar odd Oauth based error before and the only solution was to implement our own refresh token steps.

Could you confirm the oauth works if you manually get the refresh + token, and make the request with that?