AppFlowy node (only active) gives Authorization failed

Questions
1

When runnning “Test Workflow” all is right

The credentials are accepted and the AppFlowy node works as expected. But when running the same workflow as “active” prod version it fails with …

Authorization failed - please check your credentials

image
image876×383 66.6 KB

Information on your n8n setup

  • n8n version: 1.64.3
  • Database default: SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via desktop app on localhost
  • Operating system: Windows 10

Question: Anybode else experiencing this?

2

The node reports ..

401 - "fail to decode token, error:ExpiredSignature"

The way I understand AppFlowy it should get a new token by itself. My credentials are correct, otherwise running the workflow as a test would not be possible right?

3

{
“errorMessage”: “Authorization failed - please check your credentials”,
“errorDetails”: {
“rawErrorMessage”: [
“401 - "fail to decode token, error:ExpiredSignature"”
]
},
“n8nDetails”: {
“nodeName”: “AppFlowy”,
“nodeType”: “n8n-nodes-appflowy.appflowy”,
“nodeVersion”: 1,
“resource”: “databaseRow”,
“operation”: “getAll”,
“itemIndex”: 0,
“time”: “6.6.2025, 08:56:19”,
“n8nVersion”: “1.92.2 (Self Hosted)”,
“binaryDataMode”: “default”,
“stackTrace”: [
“NodeOperationError: Authorization failed - please check your credentials”,
" at ExecuteContext.execute (/home/node/.n8n/nodes/node_modules/n8n-nodes-appflowy/nodes/Appflowy/Appflowy.node.ts:850:11)“,
" at processTicksAndRejections (node:internal/process/task_queues:95:5)”,
" at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:689:27)“,
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:923:51”,
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:1259:20"
]
}
}

4

I tried almost everything such as removing content and finally solved the issue by deleting the workflow and define it again from scratch.

As an alternative a download and import will sort the same effect.

I could find no relation with the credentials. The issue originates in the workflow.

If you ask me the sticky AppFlowy token in the workflow is simply a bug.