NodeApiError: UNKNOWN ERROR - check the detailed error for more information
at Object.githubApiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Github/GenericFunctions.js:37:15)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Github/Github.node.js:1773:36)
at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:658:28)
at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:585:53
Please share the workflow
(Select the nodes and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow respectively)
Share the output returned by the last node
Information on your n8n setup
n8n version:
Database you’re using (default: SQLite):
Running n8n with the execution process [own(default), main]:
Running n8n via [Docker, npm, n8n.cloud, desktop app]:
You have not filled out the question template we provide, when you created your question you may have deleted all it and we often require this information.
Hi @chandan988, I had the same issue and it turns out that the GitHub node doesn’t play well with the new “scoped fine-grained tokens”. You need to create a “classic token”.
@Jon it’s nice that you point chandan988 to fill out the form but letting him alone with his initial issue is pity.
The template tends to be handy so we can see how n8n is running and what version is being used to rule out any bugs that we may be aware of.
The workflow will also work with fine grained tokens as long as Contents is set to Read and Write, My initial thought was maybe the workflow was changed or it was a bug with an older release.