Perplexity Node: “Bad request - please check your parameters” error with valid API key (v1.107.4)

Hi team,

I’m experiencing an issue with the built-in Perplexity node in n8n v1.107.4.

- When I try to connect my Perplexity API credentials, I get the error:  
  “Couldn’t connect with these settings. Bad request - please check your parameters.”
- I have verified that my API key is correct, has credits, and is copied directly from the Perplexity dashboard.
- I regenerated the API key and tried again, but the error persists.
- As a test, I used the HTTP Request node with the same API key (using the Authorization: Bearer header), and it works perfectly—so the key and network are not the issue.

It seems the problem is specific to the built-in Perplexity node or its credential handling in this version.

**Steps to reproduce:**
1. Go to Credentials > New > Perplexity API.
2. Paste a valid API key.
3. Try to connect/save.

**Expected:**  
Credential should connect successfully.

**Actual:**  
Get “Bad request - please check your parameters.”

Let me know if you need more details or logs!

Thanks,  
Max

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

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

i have same issue

1 Like

Seems like its just the initial test that is failing but the node is actually working - I went ahead and tested it with some input data after setting up the perplexity node and then it worked!

3 Likes

For me this is broken as well. Cannot use perplexity at all unless i use an HTTP node.

Same problem here.

same problem. Funny that it works in Personal project workflows and it doesn’t in Projects project. Same API Key. If I use a different it’s still the same.

I pasted the API key to the personal project last week and it worked. Today I tried to do something with Agents in another project, so maybe something died during this week and it cannot authenticate with perplexity api any more. I also culred the api to verify the key, and it returns output.

I am also facing the same issue.

It worked for me as well. It’s strange that it shows that credentials configuration failed but it still works when run.

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