Perplexity API key not working in n8n

[eboziev]

Describe the problem/error/question

Hi everyone,

I’m trying to integrate Perplexity API with n8n.

I have already purchased credits ($5) and successfully generated an API key.

I tested the key via curl using the official Perplexity documentation, and it works correctly (the API responds with valid results).

But when I try to connect the same key inside n8n using the Perplexity API credential, I get the error:

“Couldn’t connect with these settings – Bad request.”

It looks like the built-in Perplexity credential in n8n does not activate properly, even though the key itself is valid and working outside n8n.

I’m attaching a screenshot of the n8n credential screen.

Could you please help me understand what might be the issue? Is this a bug in the n8n Perplexity integration, or do I need to configure it differently (e.g. endpoint, headers)?

Thanks in advance!

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:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[jabbson]

Hey @eboziev hope all is well. Welcome to the community.

Does it reveal any additional information about the issue when you click on the Mode details text?

[mohamed3nan]

Hello @eboziev ,

Could you please try executing any Perplexity node operation that uses that credential after saving it?

It looks like only the connection test is failing, while the node itself works fine with the saved credentials.

Let me know if it works for you.

[eboziev]

Hey guys

You were right — the issue was only with the connection test. It shows an error when saving the credential, but the node itself works fine once connected.

I just attached the node in the workflow and it executed successfully.

Thanks a lot Everything is working great now!

[mohamed3nan]

Glad it works @eboziev! I hope this connection test issue gets resolved soon.

Kindly mark my reply as the solution. Thanks, and have a great day!

[Ayo_Olatoye]

I had the exact same problem that had me flummoxed. Reading this thread saved me from what would have been an extremely frustrating afternoon. Hope they fix the issue soon

[jabbson]

Filed a bug for this issue:

Perplexity Credentials page always fails to verify

[AdventureCEO]

I’ve been having the same issue. Thanks for the info!! Very helpful.

[jan]

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

[Train3766]

Hi Jan! Thanks for the suggestion, however it is still visible after the update to ver. 1.111.0 self hosted version. Is there an alternative solution, would be great. Thank you!

Edit: Currently feeding perplexity API key into Openrouter and using OR in N8n as a workaround.

[jabbson]

The fix is in 1.112, not 1.111.

[Train3766]

Hey Jabbson! Thank you! Will use the work around for now. Cheers!