Perplexity Node: Credential test fails, but node executes successfully

Describe the problem/error/question Perplexity Node: Credential test fails, but node executes successfully.

Steps to Reproduce:

  1. Paste the provided workflow into a new n8n canvas.

  2. Open the Perplexity node and create a new credential.

  3. Enter a valid Perplexity API Key.

  4. The connection test immediately shows the error: “Couldn’t connect with these settings”.

  5. Save the credential and close the node.

  6. Manually execute the node with any prompt.

  7. Observe that the node executes successfully.

Expected vs. Actual Result:

  • Expected behavior: The connection test in the credential window should pass and show a success message.

  • Actual behavior: The connection test fails, but the node works correctly during workflow execution, which is misleading.

What is the error message (if any)? Couldn’t connect with these settings More details

Please share your workflow

({
  "name": "Bug",
  "nodes": [
    {
      "parameters": {},
      "type": "n8n-nodes-base.manualTrigger",
      "typeVersion": 1,
      "position": [
        0,
        0
      ],
      "id": "40f8eddc-c1ee-48cb-a2d0-e1ad80c8b58f",
      "name": "When clicking ‘Execute workflow’"
    },
    {
      "parameters": {
        "model": "sonar-pro",
        "messages": {
          "message": [
            {
              "content": "Hello, world!"
            }
          ]
        },
        "options": {},
        "requestOptions": {}
      },
      "type": "n8n-nodes-base.perplexity",
      "typeVersion": 1,
      "position": [
        208,
        0
      ],
      "id": "ad14dfa4-4349-4aa3-b0b2-25feff35c1b2",
      "name": "Message a model",
      "credentials": {
        "perplexityApi": {
          "id": "***",
          "name": "Perplexity account Test"
        }
      }
    }
  ],
  "pinData": {},
  "connections": {
    "When clicking ‘Execute workflow’": {
      "main": [
        [
          {
            "node": "Message a model",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "active": false,
  "settings": {
    "executionOrder": "v1"
  },
  "versionId": "c6d3072c-1193-4083-9dc2-be9708e88904",
  "meta": {
    "templateCredsSetupCompleted": true,
    "instanceId": "b0ca96db258155fde9d8e1504e2f9784d98c4f14f240e4492644a44445135513"
  },
  "id": "9QHkw8wrxIr70RrW",
  "tags": []
})

Share the output returned by the last node

“\“Hello, World!\” is a simple program used in programming to display the text **Hello, World!** on the screen, commonly serving as an introductory exercise for beginners[1][3]. It demonstrates the basic syntax of a programming language and validates that the compiler, development environment, and basic output system are working correctly[1][3].\n\nThe tradition of using \“Hello, World!\” originated with Brian Kernighan, who used it in early programming books for languages such as B and BCPL in the late 1960s and early 1970s, notably popularizing it in \“The C Programming Language\”[2]. The program typically consists of outputting the phrase using the simplest possible statements, making it the first step for most newcomers to software development[1][3].\n\nHere is the classic **C language** example:\n\n```c\n#include <stdio.h>\nint main() {\n printf(\“Hello, World!\”);\n return 0;\n}\n```\nThis program includes the standard input/output header (`stdio.h`), defines the entry point (`main`), prints the message, and exits successfully[1][3].”

Information on your n8n setup

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

yeah that’s a common error recently.

Somehow the perplexity credential will show error when add key.

But you still can use that credential after all.

Guess just some small bug when it doing test fetch with Perplexity

3 Likes

I understand this is a low-priority bug since a workaround is available. However, from a UX perspective, it’s a critical flaw.

It creates a significant and unnecessary roadblock for anyone trying to set up the Perplexity node for the first time, causing them to doubt their own setup instead of the UI. This kind of “false negative” error can be more damaging to user trust than a clear, functional error.

I hope the team can consider raising the priority of this fix, as it directly affects the initial setup and user confidence.

4 Likes

I’m seeing this error and it doesn’t look like my AI Agent node is able to call Perplexity Tool.

Interestingly, I wasn’t able to reproduce your issue. On my end, the Perplexity tool works correctly when called by the AI Agent, despite the initial credential test failing in the UI.

It seems the UI bug with the credential test is separate from the tool’s functionality for the agent. Perhaps the issue you’re seeing is specific to your workflow’s configuration or n8n version?

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

New version [email protected] got released which includes the GitHub PR 19440.